Skip to main content
Glama

list_runs

Lists all training runs launched through gpu-bridge from the local registry, including the last recorded status so you can review past jobs and identify runs needing a live status check.

Instructions

List all training runs this MCP has launched (from the local registry).

The status shown is the last one seen; get_run_status checks a run live.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load. It usefully discloses the data source (local registry) and that status values are a cached last-seen snapshot rather than live truth, which is real value. It does not address ordering, whether empty results are possible, or whether runs from other sources appear.

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 sentences, no filler, with the scope constraint front-loaded and the staleness caveat immediately after. Every clause carries information an agent needs.

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?

An output schema exists, so return-value shape need not be described, and there are no parameters to document. The staleness caveat closes the main ambiguity; only minor gaps remain (ordering, behavior on an empty registry).

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 schema is fully self-describing for an empty argument object.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("List all training runs") plus a precise scope: runs launched by this MCP, sourced from the local registry. The scope qualifier and the mention of get_run_status make it clearly distinguishable from a live-status tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The second sentence routes the agent: this tool returns the last-seen status, while get_run_status checks a run live. That is an implicit but clear when-to-use split. It stops short of an explicit 'use this when you need an inventory' statement or any exclusion for runs launched outside this MCP.

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