Skip to main content
Glama

BRAINIAC Agent Network Float

Plan cash replenishment routes

agent-networks_cash-replenishment-route-plan

Build capacitated cash replenishment routes for caller-supplied outlets, depots, and vehicles. Distances prefer directed distances[] entries and otherwise use rounded haversine meters from coordinates, labeled supplied versus straight_line. Routes use nearest-neighbor construction, intra-route 2-opt, and a cheapest-feasible insertion pass. Optional time windows use minutes_per_distance_unit for travel. No mapping, routing, or external optimization API is called. Price $0.04 USDC. POST /api/v1/agent-networks/cash-replenishment-route-plan. 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": {
      "outlets": "<outlets>",
      "depots": "<depots>",
      "vehicles": "<vehicles>"
    },
    "name": "agent-networks_cash-replenishment-route-plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
depotsYes
outletsYes
vehiclesYes
distancesNo
minutes_per_distance_unitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 discloses the distance fallback logic and labeling ('supplied versus straight_line'), the algorithm stack (nearest-neighbor, 2-opt, cheapest-feasible insertion), the time-window travel model, the absence of external API calls, the $0.04 USDC price, the POST endpoint, and that unpaid calls return 402 without running. The remaining gap is the return payload and what happens on infeasible instances.

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 purpose, then distance semantics, then algorithm, then operational facts (no external API, price, endpoint, 402). Nearly every sentence earns its place, though the endpoint path and price could be compressed slightly.

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 optimization tool with no annotations, no output schema, and 0% schema coverage. The description covers method and inputs reasonably but leaves an agent guessing about the response shape (routes, stops, distance/cost totals?) and infeasibility behavior, which matters a lot for a capacitated VRP.

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. It explains the distances[] array semantics (directed entries, preference order, labeling) and minutes_per_distance_unit (travel time for windows), which are the two least self-evident parameters. However, it says nothing about capacity, max_stops, delivery_cost, service_minutes, window_start/end, or vehicle ready/due minutes — half the nested fields remain opaque.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Build capacitated cash replenishment routes' for 'caller-supplied outlets, depots, and vehicles'. This is clearly a VRP-style construction tool, distinguishable from the analytics siblings like float-rebalancing or cash-shortage-analysis, and the scope (capacitated, caller-supplied inputs) is precise.

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 input shape — you have outlets, depots, and vehicles and want routes. There is no explicit 'use this when...' or naming of an alternative tool, though the 'No mapping, routing, or external optimization API is called' line usefully sets expectations about what this tool is not.

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