Skip to main content
Glama

BRAINIAC Agent Network Float

Analyze liquidity cost

agent-networks_liquidity-cost-analysis

Calculate the cost of holding cash and electronic float for the supplied period. Funding from funding_rate_bps or funding_costs, replenishment costs, collection costs, and transfer fees are actual expenses. Idle capital from idle_periods and cost_of_capital_bps is an opportunity cost. Rates annualize with annualization_days (default 365): floor(balance * rate_bps * days / (10000 * annualization_days)). Currencies are never mixed. lines and formulas show every intermediate. No ledger is fetched or stored. Price $0.04 USDC. POST /api/v1/agent-networks/liquidity-cost-analysis. 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": {
      "period_days": "<period_days>",
      "agents": "<agents>"
    },
    "name": "agent-networks_liquidity-cost-analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentsYes
collectionsNo
period_daysYes
idle_periodsNo
funding_costsNo
transfer_feesNo
replenishmentsNo
annualization_daysNo
cost_of_capital_bpsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations present, the description carries the full burden and does so well: it discloses that nothing is fetched or stored, that the calculation is deterministic, that currencies are never mixed, that unpaid calls return 402 without running, and that intermediate lines and formulas are returned. It does not specify rate limits or idempotency, but the safety-relevant behavior is unusually well covered.

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 is front-loaded and each sentence carries distinct information: cost categories, formula, currency rule, output shape, storage guarantee, price, and endpoint. It is dense but not padded; the endpoint and price sentences are operational rather than descriptive, which is the only mild dilution.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a nine-parameter, annotation-free, output-schema-less calculation tool, the description supplies the pricing model, the cost taxonomy, the arithmetic, the multi-currency constraint, and the failure mode. An agent has everything needed to invoke it correctly and interpret 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 explains that funding_rate_bps/funding_costs, replenishments, collections, and transfer_fees are actual expenses while idle_periods/cost_of_capital_bps are opportunity cost, and it gives the exact annualization formula including the annualization_days default of 365. The agents array and period_days are only loosely covered, but the semantic grouping added is substantial.

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 opening sentence names a specific verb and resource: 'Calculate the cost of holding cash and electronic float for the supplied period.' That clearly distinguishes it from siblings such as float-loss-attribution or cash-shortage-analysis, though no sibling is named explicitly to route the agent.

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 by the cost-categorization detail (actual expenses vs. opportunity cost) and by 'No ledger is fetched or stored,' which signals a pure what-if calculation rather than a data-retrieval tool. However, there is no explicit statement of when to prefer this over a sibling analysis tool, and no exclusions are given.

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