Skip to main content
Glama

BRAINIAC Crypto Operations

Score bridge leg consistency

crypto-operations_bridge-leg-consistency

Group caller-supplied source and destination legs by message id. A message is consistent when both legs succeeded for the same amount. The recovery index is the hardest leg: a pending destination after a successful source scores lower than two matching successes. No chain is queried. Price $0.04 USDC. POST /api/v1/crypto-operations/bridge-leg-consistency. 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": {
      "legs": "<legs>"
    },
    "name": "crypto-operations_bridge-leg-consistency"
  }
}

Input Schema

NameRequiredDescriptionDefault
legsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 discloses that no chain is touched (side-effect-free), that the call costs $0.04 USDC, the POST path, and that unpaid calls return 402 and do not execute. It omits idempotency and rate-limit behavior, keeping it below 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?

Four short sentences, front-loaded with the grouping and scoring rule before payment and transport details. Dense and largely waste-free, though the endpoint path and price sit slightly awkwardly mid-paragraph.

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?

Input semantics and cost/behavior are well covered, but with no output schema the description should say what is actually returned — per-message verdicts, a recovery index value, or both. 'Scores lower' implies a score output without describing its shape or how many results come back.

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 does: it explains grouping by message id, that consistency requires both legs to succeed for the same amount, and the asymmetry of a pending destination after a successful source. It does not fully spell out the role/status enum meanings or the 2-80 leg bound.

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 resource: group caller-supplied source/destination legs by message id and score consistency. The agent can tell this is an offline scoring/grouping operation rather than a chain query. It does not explicitly differentiate itself from the sibling bridge-partial-failure-audit, so it stops short of a 5.

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 caller must already hold the legs ('caller-supplied') and 'No chain is queried' hints at when this is appropriate versus chain-reading tools. There is no explicit when-to-use or when-not-to-use guidance, and the sibling audit tool is never named as an alternative.

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