Skip to main content
Glama

Little’s law concurrency

bpj_system_little_law
Read-onlyIdempotent

Estimate mean in-flight requests from steady-state throughput and mean end-to-end latency.

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>",
      "latencyMs": "<latencyMs>"
    },
    "name": "bpj_system_little_law"
  }
}

Input Schema

NameRequiredDescriptionDefault
arrivalsYes
latencyMsYes

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds one genuinely useful behavioral qualifier — results are only meaningful for steady-state systems — but says nothing about what is returned (a dimensionless concurrency figure) or about the underlying L = λ·W relationship.

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 13-word sentence with the verb and output front-loaded; nothing is padding. It is lean to the point of under-specification, but no wording is wasted.

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 closed-world calculator, the core is covered, but with no output schema the description should say what comes back (a mean concurrency value, dimensionless) and note the steady-state assumption more explicitly. As written, an agent knows the gist but not the return shape.

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 schema's own titles already give units ('Mean arrivals per second', 'Mean end-to-end milliseconds') plus min/max bounds. The description restates those two quantities in prose ('throughput and mean end-to-end latency') without adding constraints, edge-case behavior, or unit caveats beyond the schema.

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 verb ('Estimate') and a precise quantity ('mean in-flight requests'), which is exactly Little's law concurrency. It is clear on its own, but it never distinguishes itself from the sibling bpj_little_law_flow_time or other system-sizing calculators, so an agent must infer which of the related tools fits.

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?

Usage is only implied: 'steady-state throughput' hints at the precondition that the system must be in steady state, and the two inputs implicitly define when the tool applies. There is no explicit when-to-use, no when-not, and no pointer to alternatives such as the flow-time sibling.

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.