Skip to main content
Glama

Serial Station Bottleneck Capacity

bpj_line_bottleneck_capacity
Read-onlyIdempotent

Compare two serial stations at steady rates and estimate queue accumulation when the upstream station runs at full speed.

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": {
      "stationA": "<stationA>",
      "stationB": "<stationB>",
      "hours": "<hours>"
    },
    "name": "bpj_line_bottleneck_capacity"
  }
}

Input Schema

NameRequiredDescriptionDefault
hoursYes
stationAYes
stationBYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so safety is fully covered. The description usefully adds that this is a steady-state ('at steady rates') analytical estimate rather than a simulation, but says nothing about whether variability, downtime, or setup time are modeled, nor what the computed result looks like.

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?

A single front-loaded sentence with no filler; the verb, the assumptions, and the outcome all appear before any elaboration. Nothing redundant, though it is arguably too terse for a three-parameter analytical tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations explaining the computation, the description should say what is returned (bottleneck station, throughput, queue growth per hour, total queue over the window). It does not, so an agent cannot anticipate the result shape or units for a tool with three required numeric inputs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 clarify that stationA is the upstream station and that rates are compared at full speed, but it never explains the 'hours' parameter (window length) or how it interacts with the two rates, leaving a third of the inputs unexplained.

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?

States a specific verb ('compare') plus two resources ('two serial stations') and names the computed output ('estimate queue accumulation'). It is distinguishable from generic capacity siblings, though it never explicitly says how it differs from bpj_system_serial_availability or bpj_compare_line_sets.

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?

The phrase 'when the upstream station runs at full speed' implies the modeling scenario in which this applies, which is useful usage context. However there are no explicit when-not conditions and no alternatives named, so an agent must infer routing from the scenario alone.

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.