Skip to main content
Glama

reconcile_base_invoice

Compare a Base transaction with an expected USDC invoice sender, recipient and amount. Returns match only after 3 confirmations. Costs 0.02 USDC on Base. Supply and persist an idempotencyKey for safe retries.

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": {
      "transactionHash": "<transactionHash>",
      "expectedSender": "<expectedSender>",
      "expectedRecipient": "<expectedRecipient>",
      "expectedAmountUSDC": "<expectedAmountUSDC>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "reconcile_base_invoice"
  }
}

Input Schema

NameRequiredDescriptionDefault
expectedSenderYes
idempotencyKeyYes
transactionHashYes
expectedRecipientYes
expectedAmountUSDCYes

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does disclose valuable traits (match only after 3 confirmations, a 0.02 USDC cost on Base, idempotency for safe retries), but omits what happens on mismatch, whether the fee is charged on failure, and any authorization or wallet prerequisites for paying the fee.

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 short sentences, each earning its place, with the core comparison front-loaded and cost plus retry safety following. Zero boilerplate or repetition.

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?

For a five-required-parameter, no-annotation, no-output-schema tool, the description covers the fee, finality depth, and retry contract, which keeps it viable. It still leaves the success/mismatch result shape and failure-side charging behavior undefined, which matters since no output schema exists to fill that 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%, so the description must compensate. It only explains idempotencyKey semantics ('supply and persist ... for safe retries') and implicitly maps the four expected-value fields; it says nothing about the transactionHash's role beyond the generic 'Base transaction', nor about amount precision or address format expectations.

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 first sentence names a specific verb (compare) plus the exact resource and comparison dimensions (Base transaction vs. expected USDC invoice sender, recipient, amount). That is far more informative than the name alone, though it does not distinguish itself from the sibling reconcile_assigned_operation.

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 implied rather than stated: verify a Base payment against an expected USDC invoice, with a mandate to persist an idempotencyKey for retries. There is no explicit when-not-to-use guidance and no pointer to the sibling reconcile tool for the alternate reconciliation case.

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