Skip to main content
Glama

operation_get

Read-onlyIdempotent

Retrieve operation progress and results after a simulation conversation, including phase, processed files/bytes, archive sizes, and timestamps; follow returned IDs and paths to inspect full records.

Instructions

Read work progress/result after any conversation. Export progress reports phase, processed files/input bytes, written archive bytes and observation time; these measure that phase, not scientific completion. Large results preserve IDs and link to operation_read; follow its paths and cursors for every detail. include_details=True returns the full record for local consumers.

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": {
      "operation_id": "<operation_id>"
    },
    "name": "operation_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
operation_idYes
include_detailsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description still adds real value by warning that the progress metrics (phase, input bytes, written bytes, observation time) measure that phase and not scientific completion, and by disclosing that large results are truncated with IDs. It stops short of describing error behavior or freshness guarantees.

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?

Front-loaded with the core action and no filler; the caveat about what the metrics mean is well placed. Sentences are dense and somewhat run-on ('Export progress reports phase, processed files/input bytes, written archive bytes and observation time'), costing a little readability but little waste.

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?

An output schema exists, so return values need not be explained, and the description does cover truncation and the include_details flag. However, it leaves the required operation_id semantics and failure modes unaddressed, which is a meaningful gap for a lookup tool whose only input is that 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 coverage is 0%, so the description must carry both parameters. It explains include_details=True (full record for local consumers) but says nothing about what operation_id is or where an agent obtains it, leaving the required parameter entirely undocumented.

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: read the work progress/result of an operation, and it clarifies the scope is 'after any conversation'. It implicitly separates itself from operation_read by saying large results 'link to operation_read' for detail, so an agent can tell the summary tool from the detail tool, though the split is not spelled out crisply.

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?

Gives a routing rule when results are large: follow operation_read's paths and cursors for every detail, and use include_details=True for the full record for local consumers. That is actionable guidance rather than a bare description, though it never states when not to call this at all (e.g. unknown/expired operation ids).

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