Skip to main content
Glama

Get Run Result

sandbase_run_get
Read-only

Get async run status and results. For Agent Services supply both service_id and run_id; succeeded, failed, and cancelled are terminal. Session items are paginated: use cursor for subsequent pages; items_available=false means retry output retrieval. Model runs use completed or failed.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNoSession items continuation cursor.
run_idYesThe run ID returned by sandbase_run.
service_idNoRequired for Agent Service runs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, closed-world access, so the safety profile is covered. Beyond that, the description discloses terminal state enums per run type ('succeeded, failed, and cancelled' vs 'completed or failed'), pagination via cursor, and the retry signal items_available=false — real behavioral context that cannot be derived from the annotations.

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?

Four short sentences, front-loaded with the core action and then layered with the conditional rules that matter. The telegraphed style ('Model runs use completed or failed') is efficient rather than wasteful, though it reads slightly like notes and could be marginally clearer.

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?

With no output schema, the description carries the burden of explaining returns, and it does so for status values, pagination, and the deferred-output case. It leaves gaps around the actual result payload and the limit parameter, but an agent can still call and interpret this tool correctly from what is given.

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 75%, so the baseline sits at 3. The description reinforces service_id's Agent Service requirement and explains cursor as a continuation mechanism, but it largely restates schema descriptions and says nothing about the limit parameter's effect or defaults.

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 and resource ('Get async run status and results') and even scopes it by run type, distinguishing Agent Service runs from model runs. It does not explicitly name sibling tools such as sandbase_runs or sandbase_run_cancel, so an agent must infer the boundary from behavior rather than from a stated alternative.

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?

Provides conditional usage detail ('For Agent Services supply both service_id and run_id') and explains how to continue pagination or retry retrieval, which is genuinely actionable. However, it never says when to prefer this over sandbase_runs (list) or when not to call it, so tool-selection guidance is only implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.