Skip to main content
Glama

get_run_status

Check whether a launched run is still alive and how many metric rows it has logged to monitor progress.

Instructions

Check whether a launched run is still alive and how many metric rows it has logged.

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

Input Schema

NameRequiredDescriptionDefault
run_nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations at all, the description carries the full burden yet only says what data comes back. It does not state that the call is read-only/non-blocking, what happens when run_name is unknown or the run has been deleted, whether polling is cheap, or whether permissions are required.

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?

One front-loaded sentence with no filler; both outputs are named in order of importance (liveness first, then row count).

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 output schema means return values need not be explained, and for a one-parameter polling tool the description is minimally sufficient. It still omits the origin of run_name and any guidance versus the many sibling status/list tools, which is the main completeness gap.

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 coverage is 0% and the single parameter 'run_name' has no description anywhere. The description never says where a run name comes from (e.g., returned by hf_push_run) or what format it takes, so the agent must guess how to obtain a valid value.

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 ('Check') and a concrete resource ('a launched run') with two named outputs: liveness and metric-row count. The agent can distinguish this from get_metrics or get_logs because it explicitly returns only a liveness flag and a row count, though no sibling is named for contrast.

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?

Usage is implied by 'launched run' - this is a polling tool for something already started - but there is no explicit statement of when to prefer it over runtime_status, get_metrics, or get_logs, and no mention of failure cases or polling cadence.

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