Skip to main content
Glama

Delivery Route Time Budget

bpj_courier_route_time_budget
Read-onlyIdempotent

Combine travel time at average driving speed with service time at each stop and compare with the route shift.

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": {
      "km": "<km>",
      "speed": "<speed>",
      "stops": "<stops>",
      "stopMin": "<stopMin>",
      "shift": "<shift>"
    },
    "name": "bpj_courier_route_time_budget"
  }
}

Input Schema

NameRequiredDescriptionDefault
kmYes
shiftYes
speedYes
stopsYes
stopMinYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish that this is a safe, read-only, idempotent, closed-world calculation. The description adds useful behavioral context by explaining that travel time and stop service time are combined and compared to the shift, but it does not state what the comparison returns, such as remaining minutes, over/under status, or a boolean feasibility result.

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 definition is a single dense sentence with no wasted clauses, and the computation is front-loaded. It could be structured slightly better by separating what is computed from what is returned, but it is appropriately sized for a simple calculator.

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?

For a five-parameter calculation with no output schema, the description explains the core formula components and the shift comparison. However, it leaves important gaps around the return value, rounding behavior, and what happens with boundary values such as zero stops or very small speeds and shifts.

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 carry parameter meaning. It does explain the relationships among speed, stops, stop minutes, and shift, which goes beyond the schema titles, but it does not explicitly map distance or the number of stops to their parameters or clarify units and edge-case handling.

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 uses a specific verb ('Combine') and names the exact resources being combined: driving travel time, per-stop service time, and the route shift. It is clear what the tool computes, though it does not distinguish itself explicitly from the many sibling time-budget tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance, no prerequisites, and no named alternatives. The phrase 'compare with the route shift' implies a feasibility check, but the agent must infer that context rather than being told when this tool is the right choice.

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.