Skip to main content
Glama

M/M/1 queue delay

bpj_system_single_queue_delay
Read-onlyIdempotent

Estimate steady-state delay and time in system for Poisson arrivals and exponential service.

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": {
      "arrivals": "<arrivals>",
      "service": "<service>"
    },
    "name": "bpj_system_single_queue_delay"
  }
}

Input Schema

NameRequiredDescriptionDefault
serviceYes
arrivalsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 behavior, so the safety profile is fully covered. The description adds that results are steady-state and that two quantities are returned, but omits the critical stability precondition (arrivals < service) and what happens when it is violated.

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 sentence with no boilerplate, front-loading both the model assumption and the two outputs. Every clause carries information.

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 simple two-parameter, read-only calculator with strong annotations and no output schema, the definition is serviceable but thin: it omits the utilization/stability constraint and does not distinguish queueing delay from time in system beyond naming both. An agent could call it but might misapply it to unstable systems.

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%, but the property titles ('Mean arrivals per second', 'Mean service completions per second') plus min/max bounds already define units and domain. The description's 'Poisson arrivals and exponential service' phrasing meaningfully ties the two parameters to rate parameters of an M/M/1 model, which is real added value, though it never uses the parameter names or explains λ vs μ roles.

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 ('Estimate') and concrete outputs ('steady-state delay and time in system') scoped to the M/M/1 model via 'Poisson arrivals and exponential service'. This identifies the queueing model clearly enough to separate it from generic siblings like bpj_system_little_law, though no sibling is named explicitly.

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 M/M/1 framing implicitly tells an agent when the tool applies (Poisson arrivals, exponential service), but there is no explicit when/when-not guidance and no named alternative for non-Poisson or multi-server cases. Nothing warns that the model requires arrival rate below service rate.

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.