Skip to main content
Glama

Backlog drain time

bpj_system_queue_drain
Read-onlyIdempotent

Estimate recovery time for an existing backlog while new jobs continue arriving.

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": {
      "backlog": "<backlog>",
      "incoming": "<incoming>",
      "service": "<service>"
    },
    "name": "bpj_system_queue_drain"
  }
}

Input Schema

NameRequiredDescriptionDefault
backlogYes
serviceYes
incomingYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the description need not restate safety. It usefully adds the modeling assumption that arrivals continue during drain, but omits the critical behavioral case where incoming rate meets or exceeds service rate (backlog never drains), which materially changes the interpretation of the result.

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; the verb and the qualifying condition appear in the first few words. Nothing could be removed without losing content.

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?

There is no output schema, so the description should say what the returned estimate represents (unit of time, and behavior when the backlog cannot drain). For a simple three-required-parameter estimator with full annotation coverage this is adequate, but the undefined failure regime leaves a real gap.

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 only loosely maps "backlog" and "new jobs continue arriving" to two of the three inputs. The service-rate parameter and the sign/edge-case constraints (e.g., zero incoming versus incoming above service capacity) are not clarified beyond what the schema titles and min/max bounds already convey.

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 a precise resource ("recovery time for an existing backlog"), plus the key modeling condition that arrivals continue. It does not differentiate itself from nearby siblings such as bpj_system_single_queue_delay or bpj_system_little_law, leaving the agent to infer which estimator applies.

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 "for an existing backlog while new jobs continue arriving" implicitly describes the scenario that selects this tool over a pure single-queue delay calculator. However, there is no explicit when-to-use/when-not guidance and no named alternative, so an agent must infer routing from the wording 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.