Skip to main content
Glama

Operation Get

operation_get
Read-only

Check durable mutation status by operation ID without retrieving or dumping the saved report content.

Instructions

Read durable mutation status without dumping the saved report content.

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

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

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, so safety is covered. The description adds one piece of real behavioral context — that the response deliberately omits the saved report payload — which helps an agent understand return scope, but says nothing about status values, terminal states, or whether polling is expected.

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 sentence with the key constraint front-loaded and no filler. It is tight, though the terseness edges toward under-specification rather than pure economy.

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?

This is a simple one-parameter read with an output schema present, so the description need not document return values, and it correctly focuses on the one thing structured fields cannot say — that report content is omitted. For a straightforward status read it is largely complete; the absence of any note on operation_id provenance is the only real gap.

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% for the single required parameter operation_id, so the schema gives only the bare name and type. The description never mentions the parameter at all — not what an operation_id identifies, where it comes from, or whether it is reusable across polls. The burden falls entirely on the naming.

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 pairs the verb "read" with a specific resource, "durable mutation status," and implicitly contrasts itself with report content retrieval ("without dumping the saved report content"). An agent can tell this is a status-polling tool rather than a content fetch, though the phrase "durable mutation" is somewhat jargon-heavy and never defines what an operation is.

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 only implied: the phrase "without dumping the saved report content" hints an agent should call this instead of report_content_get when it only needs status. There is no explicit when-to-use condition, no statement about when an operation_id exists or how long status is durable, and no named alternative.

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

Deploy Server

Other Tools