Skip to main content
Glama

devops-linux

k8s_resource_estimate

Compute total Kubernetes cluster CPU (millicores), memory (MiB/GiB), and replica footprint from deployment specs or YAML requests/limits.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "k8s_resource_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNo
cpuLimitNo1000m
replicasNo
cpuRequestNo250m
memoryLimitNo512Mi
memoryRequestNo256Mi

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden, and it discloses almost nothing: it does not say the tool is a pure read/compute operation, does not describe the shape of the returned estimate, and does not address the critical ambiguity of whether the 'text' YAML input overrides the explicit cpu/memory/replica parameters.

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

Conciseness4/5

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

A single dense sentence with the output units front-loaded and no filler. It is efficient, though the trailing 'from deployment specs or YAML requests/limits' is vague enough to add little precision.

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

Completeness2/5

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

For a 6-parameter tool with zero annotation coverage and no output schema, one sentence is thin. The agent is not told how 'text' interacts with the explicit parameters, whether a YAML document is expected, or what the response contains beyond aggregate totals.

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

Parameters2/5

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

Schema description coverage is 0% across 6 parameters, so the description must compensate. It only conveys that CPU is expressed in millicores and memory in MiB/GiB; it says nothing about the meaning of 'text', the precedence between YAML input and explicit fields, or the defaults of 1000m/250m/512Mi/256Mi/3 replicas.

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

Purpose4/5

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

The description names a specific verb (compute) and a specific output triple (cluster CPU in millicores, memory in MiB/GiB, replica footprint), plus the input sources (deployment specs or YAML requests/limits). It is clearly distinguishable from the lint/audit/generate siblings, though it does not explicitly state that distinction.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no named alternative. The phrase 'from deployment specs or YAML requests/limits' hints at acceptable input, but the agent is left to infer whether this is for capacity planning, cost estimation, or validation.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources