Skip to main content
Glama

get_run

Track subagent execution status by retrieving recorded start and end details for a specific run ID.

Instructions

実行IDの記録(開始・終了)を返す

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_id": "<run_id>"
    },
    "name": "get_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full burden of behavioral disclosure. It implies a read-only lookup but says nothing about behavior for an unknown or expired run_id, permissions, pagination, or what the returned record contains beyond start/end.

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?

A single efficient sentence with no redundant wording and the key concept front-loaded. Its brevity costs coverage, but as a structure/conciseness judgment there is nothing wasteful.

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

Completeness2/5

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

For a tool with no annotations, no output schema, and zero parameter description coverage, the definition should say more: what fields the record returns beyond 開始・終了, and error behavior. As written, an agent can guess the call shape but not what to expect back.

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?

Schema coverage is 0%, so the description must compensate for the single required run_id parameter. It does partially by establishing that the input is a 実行ID (run identifier) whose record includes start and end, but gives no format hints or examples of valid IDs.

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

Purpose3/5

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

The description names a specific verb (返す / returns) and resource (実行IDの記録, with parenthetical 開始・終了 indicating start and end), so the gist is graspable. However, "記録" is ambiguous about whether it returns only the start/end timestamps or a full run record, and nothing distinguishes it from sibling retrieval tools like get_agent or the run_* family.

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?

There is no guidance on when to use this tool, no prerequisites (e.g., a run must have been started via run_agent), and no mention of alternatives such as list_agents or wait_agents. The agent must infer usage entirely from the name and the sibling list.

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