Skip to main content
Glama

BRAINIAC Crypto Operations

Audit bridge partial failure

crypto-operations_bridge-partial-failure-audit

Compare caller-supplied source and destination records for a cross-chain bridge. Operations are matched only by message identifier, or by the log field named in fieldMapping. Amounts are scaled with the supplied decimals, fee, and optional conversion rate. consistency_status is consistent, inconsistent, incomplete, or indeterminate. risk_level is low, medium, high, or critical. A missing record is incomplete evidence, not proof that the bridge failed. No chain is queried, and no transaction is treated as final. Price $0.05 USDC. POST /api/v1/crypto-operations/bridge-partial-failure-audit. 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": {
      "source": "<source>",
      "destination": "<destination>"
    },
    "name": "crypto-operations_bridge-partial-failure-audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
feeNo
sourceYes
conversionNo
destinationYes
fieldMappingNo
expectedStatusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 declares the tool is a pure comparison over supplied data (no chain queried, nothing treated as final), defines the incomplete-evidence caveat, and discloses commercial behavior ($0.05 USDC, 402 on unpaid calls without execution). It stops short of describing the response shape beyond the two enum fields, and does not say what happens to unmatched transactions entries.

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 comparison semantics and matching rule, then caveats, then pricing and endpoint details. Sentences are dense but each carries distinct information; the ordering is slightly scattered since payment terms and the HTTP route sit after the semantic rules.

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?

There is no output schema, and the description only enumerates consistency_status and risk_level values without explaining how they are derived or what accompanies them. For a tool with a deeply nested schema (operations, transactions, receipts, logs, fieldMapping) and zero schema documentation, key structural parameters remain unexplained.

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, and it only partly does: it explains that matching keys off messageId or the log field named in fieldMapping, and that amounts use decimals, fee, and an optional conversion rate. It never mentions expectedStatus at all, nor the transactions/receipt/logs arrays, their maxItems limits, or how transaction hashes relate to operations.

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 states a specific verb and resource: compare caller-supplied source and destination records for a cross-chain bridge. It is clear what the tool does, but it never contrasts itself with the sibling crypto-operations_bridge-leg-consistency, so the agent must infer which one to pick.

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?

The description implies when this applies (caller already holds both sides of a bridge operation and wants a consistency audit) and warns that no chain is queried, so the caller must supply the data. It never states exclusions or names an alternative for adjacent needs such as single-leg checking, leaving selection to inference.

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