Skip to main content
Glama
Sign In
KubeCraft MCP Server

KubeCraft MCP Server

by cloudcrafttech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Render Network Map (PNG)

render_network

Generate a PNG image of the Kubernetes service-to-pod network map, illustrating routing via label selectors for a specified namespace or all namespaces.

Instructions

Render the service-to-pod network map as a PNG image. Shows how services route to backend pods via label selectors.

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": "render_network"
  }
}

Input Schema

NameRequiredDescriptionDefault
namespaceNoNamespace (omit for all namespaces)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the full burden. It states the tool renders a PNG image of the network map, which is straightforward. However, it does not disclose how the image is returned (e.g., base64, URL) or any potential side effects, permissions, or limitations.

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?

The description is extremely concise with two short sentences. The first sentence immediately communicates the core action and output format, and the second adds a clarifying detail. No unnecessary words.

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

Completeness3/5

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

There is no output schema, so the description should explain the return format. It mentions 'as a PNG image' but does not specify how it is delivered (e.g., inline data, URL). Given the tool's simplicity and the presence of sibling tools, this is a notable gap, but the description is otherwise adequate for basic understanding.

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% for the single 'namespace' parameter. The tool description does not add any additional meaning or usage nuance beyond what the schema already provides ('omit for all namespaces'), so it meets the baseline expectation.

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?

The description clearly states the action (Render), the resource (service-to-pod network map), and the output format (PNG image). It provides enough specificity to distinguish it from sibling tools like list_services or summarize_network_policies.

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?

The description offers no guidance on when to use this tool versus alternatives such as visualize_network, list_services, or list_pods. It does not mention prerequisites, expected outcomes, or suitable scenarios.

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