Google GKE

get_k8s_log_summary

Read-onlyIdempotent

Fetches and deduplicates container logs using pattern fingerprinting to reduce token usage. Prefer this over get_k8s_logs when triaging crashes or noisy logs.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "parent": "<parent>",
      "pod": "<pod>"
    },
    "name": "get_k8s_log_summary"
  }
}

Input Schema

Name	Required	Description
`pod`	Yes	Required. The name of the pod.
`tail`	No	Optional. Optional number of tail lines to fetch before deduplication (default 500).
`parent`	Yes	Required. The cluster that owns the pod. Format: projects/{project}/locations/{location}/clusters/{cluster}
`container`	No	Optional. Optional container name. If omitted, uses the first container in the pod.
`namespace`	No	Optional. Optional namespace of the pod. Defaults to "default" if omitted.

Output Schema

Name	Required	Description	Default
`errors`	No	Errors encountered during log retrieval and summarization.
`result`	No	JSON string representing the deduplicated log summary.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 10, 2026

TDQS

A4.2/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context beyond them: output is deduplicated via fingerprinting, so repeated lines will not appear verbatim, and token usage is reduced. It does not mention the default 500-line tail or truncation behavior, but those live in the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with zero filler. The core behavior is front-loaded and the sibling routing guidance follows immediately.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists and annotations cover the safety profile, so the description need not explain return values. It adequately covers purpose, mechanism, and sibling choice; the only minor gap is not flagging that deduplication means some log lines are omitted, which an agent should know before relying on completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so pod, parent, namespace, container and tail are all fully documented with defaults and formats. The description adds no parameter-level meaning beyond that, which is the expected baseline when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Fetches and deduplicates container logs') plus the mechanism ('pattern fingerprinting') and the benefit ('reduce token usage'), which makes it immediately distinguishable from the plain get_k8s_logs sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names the alternative and the selecting condition: 'Prefer this over get_k8s_logs when triaging crashes or noisy logs.' It lacks an explicit when-not-to-use case, such as needing the complete unfiltered log stream for exact ordering or audit purposes.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Google GKE tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?