Skip to main content
Glama

BRAINIAC Agent Network Float

Assess failed transaction disputes

agent-networks_failed-transaction-dispute

Investigate customer disputes where a charge is claimed against a failed, reversed, or pending agent transaction. Reconstruct a timeline only from supplied lifecycle events, receipts, reversals, and the dispute claim. Report conflicting evidence, missing lifecycle steps, possible duplicate receipts, and reversal inconsistencies. Successful payment is never inferred without a supplied settled fact. Price $0.04 USDC. POST /api/v1/agent-networks/failed-transaction-dispute. 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>",
      "events": "<events>"
    },
    "name": "agent-networks_failed-transaction-dispute"
  }
}

Input Schema

NameRequiredDescriptionDefault
eventsYes
disputeYes
receiptsNo
reversalsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 well: it states the evidence-only inference rule ("Successful payment is never inferred without a supplied settled fact"), enumerates the anomaly classes returned, and discloses cost ($0.04 USDC), transport (POST), and that unpaid calls return 402 without executing. It does not disclose idempotency, latency, or what happens on empty/malformed input.

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?

Purpose and scope are front-loaded in the first sentence, followed by the inference rule, then the reported findings, then operational facts. Every sentence contributes; the operational tail (price, endpoint, 402 behavior) is terse and separated rather than interleaved with the analytical contract.

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 tool with nested objects, no annotations, and no output schema, the description covers purpose, input sources, and the categories of findings reported. It stops short of describing the response shape (per-finding structure, severity, verdict field) and edge-case behavior, leaving gaps for a complex analytical tool with zero documented parameters.

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 does name all four top-level inputs (events, receipts, reversals, dispute claim) and their role in the reconstruction, but adds no meaning for nested fields — the event type enum values, amounts, provider_code, or status enums are left entirely to the schema reader.

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?

"Investigate customer disputes where a charge is claimed against a failed, reversed, or pending agent transaction" names a specific verb (investigate) and resource (failed-transaction dispute) and bounds the scope to a transaction state class. It is clear what the tool produces, though it does not name a sibling such as agent-dispute-evidence to differentiate the two.

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?

The description gives a clear triggering condition (a charge claimed against a failed, reversed, or pending transaction) and a hard input constraint: the timeline must be reconstructed "only from supplied lifecycle events, receipts, reversals, and the dispute claim." It does not state when *not* to use it or name an alternative tool, so the routing guidance is incomplete against the sibling set.

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