Skip to main content
Glama
Cloady

Cloady

Official
by Cloady

Exec Command

execCommand
Destructive

Run a one-off shell command inside a running container via Kubernetes exec to inspect or debug deployed applications without opening an interactive session.

Instructions

Run a one-off shell command in a running container (kubernetes exec).

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": {
      "workspaceSlug": "<workspaceSlug>",
      "appSlug": "<appSlug>"
    },
    "name": "execCommand"
  }
}

Input Schema

NameRequiredDescriptionDefault
envNo
regionNo
appSlugYes
requestBodyNoThe JSON request body.
workspaceSlugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true and openWorldHint=true, so the safety profile is known; the description adds only that execution happens inside a Kubernetes container. It never warns that commands run with the container's privileges and can mutate or destroy state, and says nothing about the 1000-300000 ms timeout window or how output/exit status is returned.

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 front-loaded sentence with no filler; the parenthetical earns its place by naming the underlying primitive. It is efficient, though the brevity borders on under-specification for a destructive tool.

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?

With five parameters (one nested object), no output schema, and destructive semantics, the description is too thin overall. The one thing an agent most needs to call it correctly, the shape of the requestBody and the risk/timeout posture, is left entirely to the schema and annotations.

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 only 20% and the schema has a nested requestBody, yet the description mentions no parameters at all. It gives no meaning for component, cwd, stdin, timeoutMs, env or region beyond the word 'command', so an agent must read raw schema keys to know what to send.

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?

States a specific verb and resource ('run a one-off shell command in a running container') and disambiguates the mechanism with '(kubernetes exec)'. It is clear what the tool does, though it makes no attempt to contrast itself with sibling tools.

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?

'One-off' weakly implies this is not for an interactive or long-lived shell, but there is no explicit when/when-not guidance, no mention of prerequisites such as a running/unpaused container, and no routing to alternatives like getSshSession or createSshSession for interactive access.

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