Skip to main content
Glama

BRAINIAC Agent Network Float

Attribute agent float loss

agent-networks_float-loss-attribution

Reconcile caller-supplied opening and closing cash with every cash-in, cash-out, commission, fee, reversal, and adjustment. The expected closing is the opening balance plus those signed amounts. unexplained_amount is the counted closing minus that expected closing. A supplied expected balance is compared with the same expected closing. A reversal uses the opposite sign of an earlier transaction and its own amount. Amounts are safe integers in one minor unit. No ledger is fetched or stored. Price $0.04 USDC. POST /api/v1/agent-networks/float-loss-attribution. 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": {
      "agents": "<agents>",
      "transactions": "<transactions>"
    },
    "name": "agent-networks_float-loss-attribution"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentsYes
transactionsYes

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?

With no annotations, the description carries the full burden and covers a lot: no persistence, integer minor-unit amounts, reversal sign semantics, and the $0.04 price plus 402 short-circuit. It does not describe rate limits, idempotency, or the response envelope, so a small gap remains for a paid mutation-free compute endpoint.

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?

Sentences are front-loaded and dense, leading with the computation and only then covering edge semantics and billing. Almost every clause carries information; the raw endpoint path 'POST /api/v1/agent-networks/float-loss-attribution' is the one line an agent gains nothing from.

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?

For a two-object input with nested fields and no output schema, the description explains where the key outputs come from (expected closing, unexplained_amount) and how each input class participates. Remaining gaps are cardinality limits and the exact response shape, which are moderate rather than blocking.

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 coverage is 0%, so the description must compensate and largely does: it defines opening_balance plus signed amounts as the expected closing, explains unexplained_amount as counted minus expected, and clarifies that expected_balance is compared against that same figure. It also maps the category list and the meaning of a reversal's own amount and prior reference. Identifier fields and the array size limits (200 agents / 2000 transactions) are left entirely to the schema.

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 description gives a specific verb and resource: it reconciles caller-supplied opening/closing balances against signed transaction categories and derives an unexplained amount. That is far more precise than the title alone. It does not, however, differentiate itself from nearby tools such as settlement-reconciliation, so an agent must infer the boundary.

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?

'Caller-supplied' plus 'No ledger is fetched or stored' tells the agent this is a pure computation over input data, not a lookup, which implicitly routes away from ledger-reading siblings. It also states the paid-call behavior (402 does not run). It stops short of naming a concrete alternative for when the caller lacks transaction data.

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