Skip to main content
Glama

Check a Matchaa operation

get_operation
Read-only

Use this when a Matchaa call was interrupted or returned running: reports the status of an operation in this guest space. If it failed or its lease expired, call the original tool again with exactly the same arguments to resume it without another charge.

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": {
      "guestToken": "<guestToken>",
      "operationId": "<operationId>"
    },
    "name": "get_operation"
  }
}

Input Schema

NameRequiredDescriptionDefault
guestTokenYes
operationIdYes

Output Schema

NameRequiredDescriptionDefault
errorNo
resultNo
statusYes
recoveryNo
downloadUrlNo
operationIdYes
expiresInSecondsNo
retryAfterSecondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), but the description adds genuinely new behavior: lease expiration semantics and the fact that resuming via identical arguments avoids a second charge. It does not enumerate the possible status values it can report, though the presence of an output schema reduces the need.

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, front-loaded with the triggering condition followed by the recovery action. No redundant restatement of the title or name.

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?

For a simple two-parameter polling tool with an output schema, the description covers when to use it, the recovery path, and billing implications. The remaining gap is parameter sourcing—where the caller obtains operationId—which matters given zero schema descriptions.

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%, so the description carries the full burden for guestToken and operationId—yet it never explains either. In particular it omits the crucial fact that operationId should be taken from the interrupted call's response rather than supplied arbitrarily.

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 ('reports the status of an operation') and scopes it to 'this guest space.' It also implicitly separates this from the original work tool by instructing that the original tool—not this one—should be re-invoked to resume.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives the exact trigger ('when a Matchaa call was interrupted or returned running') and the branch to take on failure or lease expiry, including the constraint to reuse identical arguments. There is no ambiguity about when this tool is appropriate versus re-calling the original tool.

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.

Resources