Skip to main content
Glama

Size a worker pool

bpj_system_worker_count
Read-onlyIdempotent

Size worker concurrency from arrival rate, per-job service time and target utilization.

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>",
      "durationMs": "<durationMs>",
      "utilization": "<utilization>"
    },
    "name": "bpj_system_worker_count"
  }
}

Input Schema

NameRequiredDescriptionDefault
arrivalsYes
durationMsYes
utilizationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare this a read-only, idempotent, closed-world, non-destructive operation, so safety is covered. Beyond that the description adds nothing behavioral: it does not say which queueing model or formula is applied, whether the result is rounded up to a whole worker count, or what assumptions (steady state, independent arrivals) bound the answer. For a computational tool those traits are the ones an agent would most want disclosed.

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, no restatement of the title, and no hedging. It is exactly as long as the content it conveys.

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 three-required-parameter calculator with rich annotations and no output schema, the definition states what goes in but not what comes out beyond 'worker concurrency' — no indication of rounding, of the returned type, or of model assumptions. It is minimally sufficient to invoke correctly but leaves real gaps for a tool whose entire value is a numeric answer.

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 compensate, and it largely does not — 'arrival rate, per-job service time and target utilization' restates the parameter titles already present in the schema. It omits unit disambiguation that matters for correctness, such as whether utilization is a fraction between 0 and 1, and does not connect the parameters in the way the actual formula does.

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 gives a specific verb and resource ('Size worker concurrency') and names the three inputs that drive the computation, so an agent knows this is a capacity-planning calculator rather than a generic counter. It stops short of distinguishing itself from adjacent sizing tools such as bpj_system_little_law or bpj_system_queue_drain, but the purpose itself is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, no mention of alternatives among the many sibling sizing tools, and no stated preconditions (for example that utilization must be below 1 for the result to be meaningful). The formula framing implies a capacity-planning context, but nothing is made explicit.

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.