Skip to main content
Glama
happypod-mcp

happypod-mcp

Official
by happy-pod

Stop pod

stop_pod
DestructiveIdempotent

Stops a pod to end compute billing while keeping its volumes, so you can halt GPU or app workloads once their jobs finish.

Instructions

Stop a pod (billing for compute stops; volumes are kept). GPU pods should be stopped as soon as their job is done.

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": {
      "podId": "<podId>"
    },
    "name": "stop_pod"
  }
}

Input Schema

NameRequiredDescriptionDefault
podIdYesPod id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the bar is lower, yet the description still adds substantive context: billing for compute ceases and volumes survive the stop. It does not say whether in-flight work is terminated gracefully or whether start_pod can revive the same pod, which are the remaining behavioral gaps.

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?

Two short sentences, purpose and cost/persistence consequence front-loaded, no filler. Every clause conveys something the agent cannot get from the schema or annotations alone.

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

Completeness4/5

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

For a one-parameter lifecycle tool with no output schema, the definition covers what the operation does, its cost effect, and what is preserved. Only the state of the pod afterward (stoppable vs. restarted via start_pod) is left unstated.

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?

There is a single required parameter with 100% schema description coverage, so the schema already carries the semantics. The description adds nothing about podId format or how to obtain it, which is acceptable at this coverage level but earns only the baseline.

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 ('Stop a pod') plus the key consequence (compute billing stops, volumes kept). That implicitly separates it from delete_pod, but no sibling is named, so differentiation is inferential rather than explicit.

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?

The line 'GPU pods should be stopped as soon as their job is done' gives a genuine when-to-use cue for one case. There is no guidance on when to prefer this over restart_pod, delete_pod, or leaving a pod running, so usage is implied rather than fully framed.

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