Skip to main content
Glama

BRAINIAC Agent Network Float

Audit shift cash handovers

agent-networks_shift-handover-audit

Audit consecutive agent shifts for cash and electronic-float handovers. Expected balances use opening amounts plus supplied transaction totals and adjustments. Actual balances prefer cash_count and electronic_float_balance when present. Missing handover records between consecutive same-agent shifts, inconsistent handed amounts, and unexplained deltas are reported. No external till balance is invented. Price $0.04 USDC. POST /api/v1/agent-networks/shift-handover-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": {
      "shifts": "<shifts>"
    },
    "name": "agent-networks_shift-handover-audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
shiftsYes
handoversNo

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 states the cost ($0.04 USDC), the 402 behavior for unpaid calls, and the exact endpoint. It also discloses a substantive behavioral guarantee — that no external till balance is invented and that deltas are only reported when unexplained — which reassures the agent about false positives. It never explicitly states that the call is non-mutating, which keeps it off 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?

Six short sentences, each carrying distinct information, with the core purpose front-loaded and the misleading-inference guard ('No external till balance is invented') placed after the mechanics. The price and endpoint could arguably be trimmed, but they are operational facts the caller needs, not padding.

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?

This is a complex two-array tool with no annotations and no output schema, so the description should also sketch what comes back — issue categories, delta amounts, per-shift or per-handover grouping. It says findings 'are reported' without describing the response shape, which leaves the agent guessing at how to consume the result.

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 names the fields that drive expected balances (opening amounts, transaction totals, adjustments) and explains that actuals prefer cash_count and electronic_float_balance. What it never covers is the handovers array semantics (from_shift_id/to_shift_id pairing, cash_handed/float_handed units, optionality), leaving a notable gap.

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?

Opens with a specific verb+resource+scope: 'Audit consecutive agent shifts for cash and electronic-float handovers.' An agent can tell this is the handover-integrity audit rather than a settlement or float-loss analysis. It stops short of naming which sibling to prefer, so it is not 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 only implied by the described computation (expected vs actual balances, missing handover detection). There is no explicit 'call this when...', no prerequisite statement about needing both shifts and handovers, and no routing guidance versus settlement-reconciliation or float-loss-attribution.

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