Skip to main content
Glama
Sign In
k8scortex-mcp

k8scortex-mcp

by apatilgtn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_cluster_info

Get the API server URL, Kubernetes version, node count, and cloud metadata for a specified cluster.

Instructions

Returns API server URL, Kubernetes version, node count, and cloud metadata for a given cluster.

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": {
      "cluster": "<cluster>"
    },
    "name": "get_cluster_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
clusterYesThe registered cluster name (e.g. prod-aks-au)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.9/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It states the tool is read-only (returns data), but fails to mention any prerequisites, potential errors, or whether the tool requires authentication. Adequate but not thorough.

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?

Single sentence, no fluff, directly conveys the tool's output. Efficient and front-loaded.

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

Completeness5/5

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

For a simple read tool with one parameter and no output schema, the description sufficiently covers the return fields (API server URL, version, node count, cloud metadata). No gaps given the low complexity.

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% (cluster parameter described). The description adds minimal extra meaning beyond 'for a given cluster' which is already implied by the schema. Baseline score of 3 is appropriate.

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?

Description clearly states it returns specific cluster metadata (API server URL, version, node count, cloud metadata). The verb 'Returns' and resource 'cluster info' are explicit. Easily distinguished from sibling tools like list_clusters or list_nodes.

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

Usage Guidelines3/5

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

Description implies usage for retrieving cluster metadata, but does not explicitly state when to use this tool versus alternatives like list_clusters or get_cluster_resource_utilisation. No when-not or exclusion criteria provided.

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

Deploy Server

Other Tools