Skip to main content
Glama

Management Span Capacity

bpj_management_span_capacity
Read-onlyIdempotent

Size the manager layer to a maximum direct-report span and compare required manager count with current coverage.

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": {
      "team": "<team>",
      "span": "<span>",
      "managers": "<managers>"
    },
    "name": "bpj_management_span_capacity"
  }
}

Input Schema

NameRequiredDescriptionDefault
spanYes
teamYes
managersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so the safety profile is covered. The description adds that the output is a comparison of required versus current managers, implying a deterministic calculation with no side effects, but it says nothing about how the comparison is expressed (gap count, surplus/deficit, rounding).

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 tight sentence with the action front-loaded and no filler. It could be split to separate the sizing step from the comparison step, but nothing 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?

With no output schema and no annotations describing returns, the description must hint at the result, which it does ('compare required manager count with current coverage'). However, it leaves the rounding rule and the exact shape of the comparison implicit, so an agent cannot predict the output precisely.

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 titles ('Maximum reports per manager', 'Individual contributors', 'Existing managers') carry the semantics. The description reinforces all three by referring to a maximum direct-report span, required manager count, and current coverage, though it never states the relationship (required = ceil(team / span)) or how managers is used.

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 action pair ('size the manager layer' and 'compare required manager count with current coverage') against a named resource, so an agent knows this is a span-of-control sizing calculator. It does not name or differentiate itself from any sibling capacity tool, which keeps it from a 5.

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 guidance on when to reach for this versus other capacity tools, no prerequisites, and no stated exclusions. The sentence describes what happens, not when an agent should choose it.

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.