Skip to main content
Glama

Little’s Law Flow Time

bpj_little_law_flow_time
Read-onlyIdempotent

Apply Little’s law to average work in process and completion rate over the same stable process boundary.

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": {
      "wip": "<wip>",
      "throughput": "<throughput>"
    },
    "name": "bpj_little_law_flow_time"
  }
}

Input Schema

NameRequiredDescriptionDefault
wipYes
throughputYes

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 readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description's only added behavioral value is the stable-boundary precondition; it does not disclose that the result is a single derived duration, its unit, or behavior on non-steady-state inputs.

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?

It is a single well-front-loaded sentence with no filler, opening on the operation and following with its inputs and condition. The compression is slightly excessive — the same sentence would cost nothing more with the output named.

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?

This is a pure calculation tool with no output schema and no annotations describing returns, so the description must state what comes back; it does not, leaving the agent to infer both the output type (a number) and its unit (implied hours via the throughput unit). The preconditions are useful but the return contract is absent.

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 is the only place semantics appear, and it does map both inputs to concepts ('average work in process', 'completion rate') plus a joint constraint that they must share a process boundary. That said, it introduces 'completion rate' where the schema says 'throughput units per hour' and never restates units, so it only partially compensates for the coverage gap.

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 names a specific operation ('apply Little's law') and the two quantities it consumes ('average work in process and completion rate'), which lets an agent tell it apart from generic flow or time converters. It never states the quantity produced (flow time, and in what unit) — that only appears in the title, so the purpose is clear but not fully self-contained.

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?

'over the same stable process boundary' implies a validity precondition (both averages must come from the same steady-state process), which is genuine when-to-use guidance. However, no alternative tool is named or excluded, so the agent gets an implied condition rather than explicit routing between this and, for example, bpj_system_little_law.

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.