Skip to main content
Glama

runtime_status

Check kernel liveness and inspect Python/CUDA, GPU, RAM, and disk status to verify a remote GPU runtime is healthy before or during training.

Instructions

Report kernel liveness, Python/CUDA info, GPU, RAM and disk on the runtime.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "runtime_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. 'Report' implies a passive read with no side effects, and listing the collected metrics signals a diagnostic probe, but the description never explicitly states it is side-effect free, whether it requires a live/connected runtime, or whether it can fail or block. Output schema exists, so return shape is covered elsewhere.

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 sentence, front-loaded with the verb and the highest-value signal (kernel liveness) before the individual metrics. No redundant or filler wording.

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 zero-parameter diagnostic with an output schema, the description covers all the substantive content: what is probed and at what granularity. The main gap is operational context — whether a runtime connection is required and when to prefer this over other status tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies no filtering or targeting arguments are needed.

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 ('Report') and enumerates the exact resources collected: kernel liveness, Python/CUDA info, GPU, RAM and disk. That is far more informative than a generic 'get status', though it never names a sibling (e.g. get_run_status, hf_space_status) to clarify which 'runtime' this applies to.

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?

The description gives no when-to-use or when-not-to-use guidance and no prerequisites (e.g. whether a runtime must be connected first). An agent can only infer diagnostics from the word 'liveness'; there is no routing toward or away from the many sibling status tools.

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