MCP Tools Reference: container.googleapis.com

Tool: list_k8s_events

Retrieves events from a Kubernetes cluster. This is similar to running kubectl events .

The following sample demonstrate how to use curl to invoke the list_k8s_events MCP tool.

Curl Request
  
curl  
--location  
 'https://container.googleapis.com/mcp' 
  
 \ 
--header  
 'content-type: application/json' 
  
 \ 
--header  
 'accept: application/json, text/event-stream' 
  
 \ 
--data  
 '{ 
 "method": "tools/call", 
 "params": { 
 "name": "list_k8s_events", 
 "arguments": { 
 // provide these details according to the tool' 
s  
MCP  
specification  
 } 
  
 } 
,  
 "jsonrpc" 
:  
 "2.0" 
,  
 "id" 
:  
 1 
 } 
 ' 
  

Input Schema

Request message for KubeEvents.

ListK8SEventsRequest

JSON representation
 { 
 "parent" 
 : 
 string 
 , 
 "name" 
 : 
 string 
 , 
 "namespace" 
 : 
 string 
 , 
 "resourceType" 
 : 
 string 
 , 
 "allNamespaces" 
 : 
 boolean 
 , 
 "limit" 
 : 
 string 
 } 
Fields
parent

string

Required. The parent cluster. Format: projects/{project}/locations/{location}/clusters/{cluster}

name

string

Optional. The name of the resource to retrieve events for.

namespace

string

Optional. The namespace of the resource. If not specified and all_namespaces is false, "default" is used.

resourceType

string

Optional. The type of the resource to retrieve events for.

allNamespaces

boolean

Optional. If true, retrieve events from all namespaces.

limit

string ( int64 format)

Optional. The maximum number of events to return. If not specified, 500 is used.

Output Schema

Response message for KubeEvents.

ListK8SEventsResponse

JSON representation
 { 
 "events" 
 : 
 string 
 , 
 "errors" 
 : 
 [ 
 { 
 object (  Status 
 
) 
 } 
 ] 
 } 
Fields
events

string

The events in string format.

errors[]

object ( Status )

Errors encountered during events retrieval.

Status

JSON representation
 { 
 "code" 
 : 
 integer 
 , 
 "message" 
 : 
 string 
 , 
 "details" 
 : 
 [ 
 { 
 "@type" 
 : 
 string 
 , 
 field1 
 : 
 ... 
 , 
 ... 
 } 
 ] 
 } 
Fields
code

integer

The status code, which should be an enum value of google.rpc.Code .

message

string

A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the google.rpc.Status.details field, or localized by the client.

details[]

object

A list of messages that carry the error details. There is a common set of message types for APIs to use.

An object containing fields of an arbitrary type. An additional field "@type" contains a URI identifying the type. Example: { "id": 1234, "@type": "types.example.com/standard/id" } .

Any

JSON representation
 { 
 "typeUrl" 
 : 
 string 
 , 
 "value" 
 : 
 string 
 } 
Fields
typeUrl

string

Identifies the type of the serialized Protobuf message with a URI reference consisting of a prefix ending in a slash and the fully-qualified type name.

Example: type.googleapis.com/google.protobuf.StringValue

This string must contain at least one / character, and the content after the last / must be the fully-qualified name of the type in canonical form, without a leading dot. Do not write a scheme on these URI references so that clients do not attempt to contact them.

The prefix is arbitrary and Protobuf implementations are expected to simply strip off everything up to and including the last / to identify the type. type.googleapis.com/ is a common default prefix that some legacy implementations require. This prefix does not indicate the origin of the type, and URIs containing it are not expected to respond to any requests.

All type URL strings must be legal URI references with the additional restriction (for the text format) that the content of the reference must consist only of alphanumeric characters, percent-encoded escapes, and characters in the following set (not including the outer backticks): /-.~_!$&()*+,;= . Despite our allowing percent encodings, implementations should not unescape them to prevent confusion with existing parsers. For example, type.googleapis.com%2FFoo should be rejected.

In the original design of Any , the possibility of launching a type resolution service at these type URLs was considered but Protobuf never implemented one and considers contacting these URLs to be problematic and a potential security issue. Do not attempt to contact type URLs.

value

string ( bytes format)

Holds a Protobuf serialization of the type described by type_url.

A base64-encoded string.

Tool Annotations

Destructive Hint: ❌ | Idempotent Hint: ✅ | Read Only Hint: ✅ | Open World Hint: ❌

Create a Mobile Website
View Site in Mobile | Classic
Share by: