Skip to main content
Glama

adaptorch_get_run

Read-onlyIdempotent

Retrieve a run summary by run_id to inspect an orchestrated AdaptOrch run's status and results quickly.

Instructions

Get run summary by run_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": "adaptorch_get_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYes

Output Schema

NameRequiredDescriptionDefault
modelNo
run_idYes
statusYes
topologyNo
cse_stateNo
created_atNo
started_atNo
consistencyNo
duration_msNo
error_classNo
finished_atNo
artifact_urlsNo
result_statusNo
synthesis_modeNo
artifact_statusNo
correctness_wallNo
collection_statusNo
evaluation_statusNo
first_run_receiptNo
synthesis_mode_usedNoServing-layer selected mode as reported by the parent; not proof of final engine execution.
auto_synthesis_reasonNo
score_validity_statusNo
model_selection_sourceNo
request_idempotency_keyNo
synthesis_mode_requestedNo
verification_diagnosticsNoOptional bounded observations. project_report is an untrusted project claim; process_spawn is a verifier launch observation. Neither changes a verdict.
verification_diagnostics_schema_versionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that — no note on behavior for unknown run_ids, error handling, or whether results are cached/live despite openWorldHint=true.

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 front-loaded sentence with no filler, which is structurally efficient. It is terse to the point of under-specification, but nothing is wasted.

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?

An output schema exists, so return values need no explanation, but with 8 sibling tools and zero parameter documentation the description leaves the agent without enough context to pick this tool confidently or supply a valid run_id.

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 description coverage is 0%, so the single run_id parameter is undocumented in structured data. The description only repeats the parameter name ("by run_id") without stating its format or where an agent obtains 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?

The description names a specific verb and resource ("Get run summary") plus the key parameter, so an agent knows it retrieves a single run's summary. It does not distinguish itself from siblings like adaptorch_list_runs or adaptorch_get_artifacts, so it falls short of a 5.

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 instead of adaptorch_list_runs (for enumerating runs) or adaptorch_run (for execution details). The agent must infer the choice purely from the tool name.

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