Skip to main content
Glama

BRAINIAC Agent Network Float

Build agent dispute evidence

agent-networks_agent-dispute-evidence

Package caller-supplied agent and operator records into a chronological evidence timeline for financial disputes. Balance transitions are checked against intervening signed amounts. Conflicting references, unexplained balance changes, and missing records for declared dispute categories are labeled separately from verified supplied facts. No liability outcome is assigned and no compensating transactions are invented. Price $0.04 USDC. POST /api/v1/agent-networks/agent-dispute-evidence. 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": {
      "dispute": "<dispute>",
      "records": "<records>"
    },
    "name": "agent-networks_agent-dispute-evidence"
  }
}

Input Schema

NameRequiredDescriptionDefault
disputeYes
recordsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it discloses a lot: balance transitions are cross-checked against intervening signed amounts, anomalies are labeled separately from verified facts, and no liability or compensating entries are produced. It also covers operational behavior (POST endpoint, $0.04 USDC, unpaid calls return 402 and do not execute). What is missing is whether anything persists server-side and whether output ordering/format is deterministic.

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 purpose, then layered with validation rules, scope limits, and finally operational details (price, endpoint, 402 behavior). Every sentence carries information; the only minor inefficiency is that pricing and endpoint metadata sit in the prose rather than being assumed elsewhere.

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 complex nested input with no annotations and no output schema, the description covers the processing logic and scope limits well, including how conflicts and missing records are separated from verified facts. It does not describe the returned structure (timeline entry shape, ordering guarantees, how labels are represented) or limits like the 5000-record cap, leaving an agent uncertain about the response.

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% against a nested two-parameter body, so the description has to compensate and only partly does: it explains that declared dispute 'categories' drive missing-record flagging and that signed amounts are validated against balance transitions, which adds real meaning to the 'amount', 'balance', and 'categories' fields. Many fields (id, currency, reference, opened_at, record 'kind') receive no semantic guidance beyond the schema itself.

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?

The description opens with a specific verb and resource: 'Package caller-supplied agent and operator records into a chronological evidence timeline for financial disputes.' An agent can immediately tell this apart from siblings like settlement-reconciliation or failed-transaction-dispute, since this one assembles supplied records into an evidence artifact rather than reconciling or diagnosing.

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?

Usage context is clear ('for financial disputes', input must be caller-supplied records) and the scope exclusions 'no liability outcome is assigned' and 'no compensating transactions are invented' tell the agent what this tool will not do, which is useful selection signal. It stops short of naming an alternative sibling or stating explicit when-not-to-use conditions, so it is not a 5.

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