Skip to main content
Glama
Sign In

Runcrate

by io.github.aeonmindai
OverviewDiscussionsAdmin

Get a cluster kubeconfig

get_cluster_kubeconfig
Read-onlyIdempotent

Get the kubeconfig of a ready cluster whose stack is kubernetes. Its server is https://127.0.0.1:6443, so kubectl on the user's computer needs the returned tunnel command (an SSH port forward to the head) running first. Returns { kubeconfig, tunnel }: save kubeconfig to a file and set KUBECONFIG to it. It grants admin on the cluster, so treat it as a secret. kubectl also runs without a tunnel through ssh_execute on the head node.

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": {
      "id": "<id>"
    },
    "name": "get_cluster_kubeconfig"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCluster ID
workspaceNoWorkspace ID (optional: defaults to the authenticated workspace)
environmentNoEnvironment name (optional: defaults to the environment this session acts in)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations by disclosing that the credential grants admin on the cluster and must be treated as a secret, plus the connectivity requirement that the tunnel must be running first. These are exactly the behavioral facts an agent needs and cannot infer from structured fields.

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?

Front-loads the purpose, then prerequisites, return shape, and security handling in a logical order with no filler. Slightly dense packing of return shape and handling instructions into single sentences costs it the top mark.

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?

Covers everything an agent needs for a credential-fetching tool with no output schema: the returned fields ({ kubeconfig, tunnel }), how to consume them (save to file, set KUBECONFIG), the security constraint, and the tunnel prerequisite.

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 coverage is 100%, so the schema already documents id, workspace and environment including their defaults. The description adds no parameter-level detail such as what happens when a workspace/environment mismatch occurs, so the baseline 3 applies.

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 ('Get the kubeconfig of a ready cluster whose stack is kubernetes'), and the qualifying conditions (ready, kubernetes stack) distinguish it clearly from siblings like get_cluster or ssh_execute.

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?

Explains the operating context: kubectl on the user's machine needs the returned tunnel command running because the server is https://127.0.0.1:6443, and it names an alternative path (kubectl via ssh_execute on the head node without a tunnel). It stops short of stating what to do when the cluster is not ready or not kubernetes, which keeps it from a 5.

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

All Runcrate toolsInspect
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