Skip to main content
Glama

Dock Door Shift Load

bpj_dock_door_shift_load
Read-onlyIdempotent

Convert inbound truck unload time into required parallel dock doors and excess minutes over available door capacity.

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": {
      "trucks": "<trucks>",
      "unload": "<unload>",
      "shift": "<shift>",
      "docks": "<docks>"
    },
    "name": "bpj_dock_door_shift_load"
  }
}

Input Schema

NameRequiredDescriptionDefault
docksYes
shiftYes
trucksYes
unloadYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive behavior, so the safety profile is covered. Beyond that, the description only discloses that two quantities are produced; it says nothing about how doors are rounded, whether truck work can be split across doors, or how over-capacity is computed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; every clause contributes either the input or one of the two outputs.

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?

No output schema exists, so the description must communicate returns, and it does name both result quantities. However, for a four-parameter computation with no schema descriptions, it leaves the output shape (single object vs. two values) and rounding semantics undefined.

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?

With 0% schema description coverage, the description carries real weight: it ties trucks and unload minutes to a door requirement measured against shift minutes and available doors, effectively mapping all four parameters. It still omits units and constraints (e.g., zero trucks, zero unload time) that would complete the mapping.

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 ("Convert") and names both the input (inbound truck unload time) and the two computed outputs (required parallel dock doors, excess minutes over capacity). An agent can tell this is a capacity-sizing calculation, though it does not explicitly contrast itself with any sibling tool.

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 or when-not-to-use guidance, and no named alternative. The scenario (dock scheduling under a shift constraint) is only implied by the wording "over available door capacity".

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.