Skip to main content
Glama

BRAINIAC Agent Network Float

Rebalance agent float

agent-networks_float-rebalancing

Propose the cheapest cash transfers that lift every agent to its minimum float after expected demand. projected_before is cash_balance minus expected_demand. Surplus is cash above the minimum; shortage is the shortfall below the minimum. Allowed corridors come only from transfer_costs. transfer_limits cap a corridor. maximum_float caps how much a receiver can take. budget caps total transfer cost. Currencies are never mixed. Allocation is successive shortest-path min-cost flow on the surplus-to-shortage network. The response is a proposal only; no transfer is initiated. feasibility explains when shortages remain. Price $0.04 USDC. POST /api/v1/agent-networks/float-rebalancing. 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>",
      "transfer_costs": "<transfer_costs>"
    },
    "name": "agent-networks_float-rebalancing"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentsYes
budgetNo
transfer_costsYes
transfer_limitsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations, the description fully carries the behavioral burden: no transfer is initiated, currencies are not mixed, corridors and limits constrain allocation, and shortages may remain. It also discloses the min-cost-flow algorithm, price, HTTP endpoint, and that unpaid calls return 402 without running.

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?

The purpose is front-loaded, and the short sentences efficiently cover definitions, constraints, side effects, and payment behavior. The dense single paragraph is somewhat difficult to scan, but there is little redundant wording.

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 complex optimization tool, the definition supplies enough algorithmic, constraint, safety, and payment context to support a correct invocation. Because there is no output schema, however, the brief references to a proposal and feasibility leave the response structure and the representation of proposed transfers underexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 0% schema description coverage, it defines projected_before, surplus, and shortage and explains the roles of expected_demand, transfer_costs, transfer_limits, maximum_float, and budget. These explanations cover nearly all consequential input semantics rather than merely restating field names.

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 specifies the action ('Propose'), resource ('cash transfers'), optimization objective ('cheapest'), and target state (minimum float after expected demand). This substantively distinguishes it from shortage analysis or route planning, but it does not explicitly contrast any sibling tools.

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?

The minimum-float and expected-demand framing makes the intended planning scenario clear, while 'proposal only' warns against using it to execute transfers. There are no explicit when-not conditions or named alternatives for adjacent cash-management tasks.

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