Skip to main content
Glama

BRAINIAC Route & Delivery Optimisation

Delivery slot capacity

route-optimization_delivery-slot-capacity
Read-onlyIdempotent

Estimate bookable orders per zone and time slot from vehicle time, service, drive and stem assumptions. Price $0.02 USDC. POST /api/v1/route-optimization/delivery-slot-capacity. An unpaid call returns the x402 payment terms and does 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": {
      "zones": "<zones>",
      "slots": "<slots>"
    },
    "name": "route-optimization_delivery-slot-capacity"
  }
}

Input Schema

NameRequiredDescriptionDefault
slotsYesslots, array. Required.
zonesYeszones, array. Required.
bookedNobooked, array. Optional.
bufferPctNobufferPct, number, from 0 to 0.9. Optional.
stemEverySlotNostemEverySlot, boolean. Optional.

Output Schema

NameRequiredDescriptionDefault
slotsNoslots. Array.
sourcesNosources. Array.
limitationsNolimitations. Array.

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?

Annotations already declare readOnly, idempotent and non-destructive, so the safety burden is light; the description nonetheless adds critical operational facts the annotations cannot convey: the $0.02 USDC price, the POST endpoint, and that an unpaid call returns x402 payment terms without executing.

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?

Four short sentences, front-loaded with purpose, then price, then endpoint, then payment-failure behavior. No filler, though the raw endpoint path adds little beyond the tool identity.

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?

With an output schema and full schema coverage, the description only needs to cover cost and invocation protocol, which it does. Minor gap: the effect of the optional 'booked' parameter and bufferPct on the returned capacity is never characterized.

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 coverage is 100%, so the per-field meanings are already documented. The description hints that vehicle time, service and drive assumptions drive the result, but adds nothing about bufferPct, stemEverySlot, or how the optional 'booked' array is applied.

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: estimate bookable orders per zone and time slot, and names the driving inputs (vehicle time, service, drive, stem assumptions). That is clearly distinct from the sibling optimization/VRP tools, which compute routes rather than capacity.

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 as capacity planning before accepting bookings, but there is no explicit when-to-use or when-not-to-use guidance relative to siblings, nor any statement of how existing 'booked' orders interact with the estimate.

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