Skip to main content
Glama

BRAINIAC Route & Delivery Optimisation

Assign routes to drivers

route-optimization_driver-shift-assign
Read-onlyIdempotent

Assign pre-built routes to drivers by shift, skills and vehicle type with min-cost Hungarian matching. Price $0.03 USDC. POST /api/v1/route-optimization/driver-shift-assign. 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": {
      "routes": "<routes>",
      "drivers": "<drivers>"
    },
    "name": "route-optimization_driver-shift-assign"
  }
}

Input Schema

NameRequiredDescriptionDefault
routesYesroutes, array. Required.
driversYesdrivers, array. Required.
skillModeNoskillMode, string, one of strict, soft. Optional.
skillPenaltyNoskillPenalty, number, from 0 to any. Optional.
allowMultipleNoallowMultiple, boolean. Optional.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
totalCostNototalCost. Number.
unassignedNounassigned. Array.
assignmentsNoassignments. 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 behavior, so the safety profile is covered. The description adds genuinely non-obvious operational context: the $0.03 USDC price, the x402 payment flow, and that an unpaid call returns payment terms without executing — valuable for an agent deciding whether a call will actually run.

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?

Three tightly packed sentences with the core purpose front-loaded, then cost/payment, then endpoint. The literal POST path is mildly redundant given the tool already targets that endpoint, but overall there is little 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?

An output schema exists, so return shape needn't be described, and the payment/billing behavior is disclosed. The main residual gap is that the optimization knobs (skillMode semantics, penalty effect, allowMultiple behavior) are not explained, though the schema carries them at full coverage.

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 100%, so the baseline is 3. The description does add meaning by naming the matching dimensions (shift, skills, vehicle type), but the per-parameter specifics like skillMode strict vs soft, skillPenalty, and allowMultiple are left entirely to the schema.

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 ('Assign pre-built routes to drivers') plus the matching criteria and algorithm ('min-cost Hungarian matching'). The 'pre-built routes' phrasing distinguishes it from route-construction siblings such as vrp-capacitated or tsp-optimize, so the agent knows it consumes existing routes rather than generating them.

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?

'Pre-built routes' implies a prerequisite (routes must already exist), which gives implicit guidance on when this tool fits. However, there is no explicit when-to-use/when-not or named alternative among the many sibling tools, so the agent must infer positioning.

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