Skip to main content
Glama

reconcile_assigned_operation

Check settlement evidence for a pending 402Mob operation using its x402 settlement transaction hash. Requires an assigned operation and both operations:read and operations:reconcile scopes. This does not submit payment.

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": {
      "operationId": "<operationId>",
      "transaction": "<transaction>"
    },
    "name": "reconcile_assigned_operation"
  }
}

Input Schema

NameRequiredDescriptionDefault
operationIdYes
transactionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observed

TDQS

B3.4/5.0
Behavior2/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 discloses scope requirements and that no payment is submitted, which is useful, but says nothing about whether reconciling mutates server state, what happens on a hash mismatch, idempotency, or what evidence is returned — significant gaps for a tool whose name implies reconciliation (a state-affecting act) while its text describes a 'check'.

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?

Three tight sentences, front-loaded with purpose, followed by prerequisites and a critical negative constraint. No filler and nothing buried.

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 annotations, no output schema, and two undocumented parameters, the description should do more. It covers purpose, scopes, and the no-payment constraint, but leaves the return value, mutation semantics, and failure modes unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it largely does: it identifies 'transaction' as the x402 settlement transaction hash and constrains 'operationId' to an assigned, pending operation. It stops short of explaining what 'assigned' or 'pending' mean operationally or whether the operation must be in a particular state.

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 object ('Check settlement evidence') plus the resource ('pending 402Mob operation') and the key input ('x402 settlement transaction hash'). The closing 'This does not submit payment' quietly separates it from payment-submitting siblings, but no sibling is named explicitly, so differentiation is inferred rather than stated.

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?

Gives real preconditions — the operation must be assigned and both operations:read and operations:reconcile scopes are required — and rules out use as a payment tool. It never says when to choose this over read_assigned_operation_evidence or what to do when no settlement evidence exists, so usage is only implied.

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