Skip to main content
Glama

results_get

Read-onlyIdempotent

Retrieve a task's current result artifacts, previews, checks, replacement history, missing requirements, and recent analysis methods so you can verify completion or hand off simulation results.

Instructions

Resume analysis and delivery: current artifact paths/previews, checks, replacement history, missing requirements, recent analysis methods and imported project records. Archives are finally verified by completion_check. Use task_records for older analyses.

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": {
      "task_id": "<task_id>"
    },
    "name": "results_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered without prose. The description adds scope context by saying results are 'current'/'recent' and that completion_check performs final verification, which is useful. It does not disclose how much history counts as 'recent' or how the returned bundle is organized.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single compact passage with no filler, and the cross-references are placed at the end where they belong. However, the front-loaded clause 'Resume analysis and delivery' is vague and the remaining content is a dense comma list of return items, which reads as a data dump rather than a structured statement of purpose.

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?

With an output schema present and strong annotations, the description need not explain return values in detail, and it covers sibling routing adequately. The clear gap is task_id, which is required yet undocumented anywhere, leaving the agent to guess its semantics.

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?

There is exactly one parameter, task_id, with 0% schema description coverage, and the description never mentions it or explains what a task id refers to. With the schema providing no guidance, the description had the full burden of explaining the parameter and does not meet it.

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 the resource returned (current artifact paths/previews, checks, replacement history, missing requirements, recent analysis methods, imported project records), which is far more specific than the name results_get alone. The leading phrase 'Resume analysis and delivery' is cryptic and blurs whether the tool fetches state or restarts work, so the read-only nature of the operation has to be inferred from the annotations rather than the prose.

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?

It explicitly routes the agent to task_records for older analyses and to completion_check for final archive verification, giving two clear boundaries against siblings. It never states the positive trigger case directly (e.g. 'call this to fetch the current results for a task'), so the when-to-use is implied by the enumeration rather than declared.

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