Skip to main content
Glama

Check a 37Soul operation

get_operation

Retrieve the final result of a queued or running chat or post operation by passing the operation_id returned by chat_with_host or instruct_post.

Instructions

Check the final result of a chat or post operation that is still queued or running. Use the operation_id returned by chat_with_host or instruct_post.

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

Input Schema

NameRequiredDescriptionDefault
operation_idYesThe operation id returned by chat_with_host or instruct_post.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.15.3
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / operation_id / maximum
      Added value: +9007199254740991
  2. Addedv0.11.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses the async lifecycle (operations can be queued or running and this retrieves the final result), but it does not say what happens if the operation is still incomplete — whether it blocks, returns a status field, or errors — which is the single most important behavior for a polling tool.

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

Conciseness5/5

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

Two sentences, no filler, with the core action and its state condition front-loaded before the parameter provenance. Nothing could be removed without losing information.

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 no output schema and no annotations, the description must cover both behavior and result shape, and it only says 'final result' without indicating the fields returned or how a pending state is represented. Adequate to select and invoke the tool, but an agent polling in a loop is left guessing about incomplete-state semantics.

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?

There is one parameter at 100% schema coverage, and the schema already documents that operation_id comes from chat_with_host or instruct_post. The description restates that provenance rather than adding new meaning (valid range, retry behavior after failure, id lifetime), so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Check the final result of a chat or post operation') and scopes it to operations that are 'still queued or running'. It also names the two sibling tools (chat_with_host, instruct_post) whose output feeds this one, so an agent can place it precisely in the workflow.

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?

Clear trigger condition: use this when a previously submitted chat or post operation has not yet finished, using the operation_id from chat_with_host or instruct_post. It lacks an explicit negative case (e.g. 'do not call with an id from list_hosts' or 'do not poll more than N times'), so it stops short of full when/when-not guidance.

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