Skip to main content
Glama

stop_run

Terminate a running training job by run name; for Hugging Face jobs, this ends billing for the run.

Instructions

Terminate a running training job (for a Hugging Face job this stops its billing).

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": {
      "run_name": "<run_name>"
    },
    "name": "stop_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations supplied, the description must carry the full behavioral burden, and it does add one genuinely non-obvious fact: that stopping a Hugging Face job halts billing. It omits the important remaining traits — whether termination is irreversible, what happens to checkpoints/artifacts, and whether the run must be in a particular state to be stopped.

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?

One sentence, front-loaded with the action, with a parenthetical that earns its place by adding the billing consequence. There is no filler, though the payoff is limited because the brevity leaves the gaps noted above.

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?

The existence of an output schema relieves the description of explaining return values, and the destructive nature of a stop is implicit in the verb. However, for a destructive one-parameter tool with no annotations and no schema documentation, it should at minimum address irreversibility and run_name format.

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 0% for the single parameter, so the description should explain what run_name is (an identifier, a display name, a slug) and where to obtain it. It says nothing about the parameter, leaving the agent to infer the accepted format from the schema's bare string type.

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?

The description uses a specific verb (terminate) against a specific resource (a running training job), so the operation is unambiguous. It does not distinguish itself from near-identical siblings such as hf_job_cancel, hf_runtime_stop, or runtime_stop, leaving the agent to guess which surface applies to which job type.

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?

Usage is only implied by the phrase 'running training job' — there is no explicit when-to-use, when-not-to-use, or pointer to an alternative among the several cancel/stop siblings. An agent cannot tell from this text whether to prefer hf_job_cancel for HF jobs or whether this tool covers them too.

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