Skip to main content
Glama

get_agent

Fetch a started child agent's current status and final result by job ID; include progress events or usage details only when explicitly requested.

Instructions

開始した子の状態と最終結果だけを取得する。途中イベントはinclude_events、使用量等はinclude_detailsを明示した場合だけ返す。本文は開始したサーバーのメモリに保持

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": {
      "job_id": "<job_id>"
    },
    "name": "get_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes
after_eventNo
include_eventsNo進捗イベントとlastSequenceを返す。既定false
include_detailsNo使用量・実行メタデータを返す。既定false

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations at all, the description carries the full load and does well on the most important trait: the default response is deliberately minimal (status plus final result only), and richer payloads require explicit opt-in flags. The note that the body is held in the memory of the server that started it is a genuinely useful operational caveat, hinting at retention limits; it stops short of stating what happens when the job is unknown or the server has restarted.

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?

Three compact sentences, front-loaded with the default behavior and followed by the opt-in flags and the storage caveat. Every sentence carries weight; only minor tightening would be possible.

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?

For a four-parameter read tool with no annotations and no output schema, the definition covers defaults and data residency but leaves meaningful gaps: the set of possible status values, behavior on an invalid or expired job_id, and the meaning of after_event. An agent could call it correctly but cannot predict the response shape or error modes.

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 50%: include_events and include_details are already documented in the schema, and the description largely restates them (defaults plus what they return) rather than adding new syntax or semantics. The two undocumented parameters, job_id (child job identifier) and after_event, get no explanation, with after_event's paging role left entirely unaddressed.

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 names a specific verb and resource: retrieve the status and final result of a started child agent, with the 'だけ' qualifier making clear it is a narrow read. It does not, however, distinguish itself from the closely related wait_agents or get_run siblings, which is a real ambiguity for an agent choosing between them.

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 rather than stated: the reader learns that events and usage metadata come only when include_events or include_details are set explicitly, which signals the default lightweight use case. There is no explicit statement of when to prefer this over wait_agents (blocking wait) or get_run, and no mention of prerequisites such as the job having been started.

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