Skip to main content
Glama

BRAINIAC Agent Network Float

Allocate outlet capacity

agent-networks_outlet-capacity-allocation

Distribute caller-supplied demand across outlets that share the demand location, support the service type, and have operating hours in the interval. Interval capacity is capacity_per_hour times hours, and when staffing is supplied it is also limited by staff_count times staff_capacity_per_hour times hours. Demand is allocated in demand id order to the eligible outlet with the most remaining capacity, then by outlet id. utilization_bps is floor(allocated * 10000 / capacity). capacity_required is the extra allocated volume still needed to reach each supplied fulfil_bps target. No map, geocoder, or demand database is used. Price $0.04 USDC. POST /api/v1/agent-networks/outlet-capacity-allocation. 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>",
      "demand": "<demand>"
    },
    "name": "agent-networks_outlet-capacity-allocation"
  }
}

Input Schema

NameRequiredDescriptionDefault
demandYes
outletsYes
service_level_targetsNo

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 deterministic allocation rule (demand id order, then most remaining capacity, then outlet id), the floor rounding for utilization_bps, the no-external-lookup behavior, the $0.04 USDC price, and that unpaid calls return 402 without running. It does not state whether the call mutates any state, idempotency, or rate limits, which is the remaining gap.

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 description is dense but front-loaded: allocation logic first, derived metrics second, constraints and pricing last. Nearly every clause carries information an agent needs to predict output. The sentences are long and run together with commas, which slightly hurts scannability but does not add waste.

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?

This is a moderately complex tool with three nested-array parameters, no output schema, and no annotations. The description covers eligibility, the allocation tie-break, both derived output fields, the input-only nature of the call, and the payment gate. What is missing is the overall response shape beyond utilization_bps and capacity_required, which matters because no output schema exists to fill that in.

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 for the semantically important fields: it explains how outlet capacity is derived from capacity_per_hour times hours, how staff_count and staff_capacity_per_hour further cap it, what demand.transactions drives, and what fulfil_bps targets produce (capacity_required). It does not define every field, e.g. it never explains interval_id or service_type matching beyond the eligibility sentence, but the high-value parameters are covered.

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 opens with a specific verb and resource: 'Distribute caller-supplied demand across outlets' plus the three eligibility criteria (shared location, service type, operating hours in interval). That is far more precise than the name alone. It stops short of naming a sibling it replaces, but the allocation semantics make it distinguishable from the detection/benchmark/risk tools in the catalog.

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?

It states a key precondition implicitly by saying 'caller-supplied demand' and explicitly that 'No map, geocoder, or demand database is used,' which tells an agent this is a pure computation over provided input. However, there is no explicit when-to-use versus when-not guidance and no named alternative, so usage must be inferred from the algorithmic description.

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