Skip to main content
Glama

BRAINIAC Agent Network Float

Reconcile agent settlements

agent-networks_settlement-reconciliation

Reconcile caller-supplied agent transactions against provider settlement statement rows. Confirmed matches require a unique settlement.transaction_id, a unique settlement.reference equal to transaction.settlement_reference, or a unique currency+amount pair. Ambiguous candidates are listed separately and are never treated as confirmed. Amount and fee deltas, missing settlements, unmatched credits, and duplicate reference groups are returned with evidence. No FX conversion is applied. Price $0.04 USDC. POST /api/v1/agent-networks/settlement-reconciliation. Unpaid calls return 402 and do not run.

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": {
      "transactions": "<transactions>",
      "settlements": "<settlements>"
    },
    "name": "agent-networks_settlement-reconciliation"
  }
}

Input Schema

NameRequiredDescriptionDefault
settlementsYes
transactionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it defines the three confirmation criteria, states that ambiguous candidates are never treated as confirmed, discloses that no FX conversion happens, and adds operational facts (POST endpoint, $0.04 USDC price, 402 on unpaid calls with no execution). It stops short of covering idempotency, whether anything is persisted, or rate/size limits, so not a 5.

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?

Front-loaded with the core action and the matching criteria, then result categories, then the constraint and billing facts. Every sentence carries information, though the telegraphic, semicolon-free run of clauses about outputs is dense and could be split for scannability.

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?

There is no output schema, so the description properly enumerates what comes back (confirmed matches, separately listed ambiguous candidates, amount/fee deltas, missing settlements, unmatched credits, duplicate reference groups with evidence). For a two-input compute tool that is close to complete; only error behavior beyond the 402 case and any output structure remain unspecified.

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?

Schema description coverage is 0%, so the description must compensate. It names specific nested fields and their roles — settlement.transaction_id, settlement.reference vs transaction.settlement_reference, and the currency+amount fallback — which adds real meaning about which fields drive matching. However, it says nothing about other declared fields (id, fee, kind, agent_id, settled_at) or the 5000-item caps and signed amount ranges, leaving meaningful semantics undocumented.

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?

"Reconcile caller-supplied agent transactions against provider settlement statement rows" gives a specific verb plus both input resources, and the surrounding sibling list is entirely different analytical tools, so the agent can distinguish this one immediately. The description also names the concrete output categories (deltas, missing settlements, unmatched credits, duplicate reference groups), reinforcing what the tool produces.

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: the matching rules tell you what the tool will do, and "No FX conversion is applied" implicitly excludes single-currency-mismatched work, but there is no explicit "use this when / do not use this when" and no named alternative. An agent can infer the applicability from the reconciliation semantics, which is adequate but not directive.

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