Skip to main content
Glama

Sprint Capacity

bpj_sprint_capacity
Read-onlyIdempotent

Estimate sprint hours available for delivery after team absence, recurring duties, and a contingency reserve.

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": {
      "people": "<people>",
      "days": "<days>",
      "hoursPerDay": "<hoursPerDay>",
      "absence": "<absence>",
      "overhead": "<overhead>",
      "reserve": "<reserve>"
    },
    "name": "bpj_sprint_capacity"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysYes
peopleYes
absenceYes
reserveYes
overheadYes
hoursPerDayYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already declare this as a safe, idempotent, closed-world calculation, so the description adds the meaningful remainder: the calculation is total capacity reduced by three named deductions. It does not state how the three inputs interact arithmetically (whether reserve is applied to gross or net hours, or whether absence and overhead are summed), which is the main behavioral unknown for a formula tool.

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 front-loaded sentence with no filler, and the deduction sequence is listed in the order an agent would reason about it. It is efficient rather than padded, though its terseness is part of why the parameter story is thin.

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?

Six required parameters at 0% schema coverage and no output schema, so the description must explain both inputs and the returned units. It explains neither the three capacity-defining inputs nor what the returned number represents (per-sprint total, per-person, rounding, or unit), leaving an agent able to pass arguments but unable to predict the result.

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% and six parameters are required, so the description carries the full burden. It only maps to three inputs (absence to "team absence hours", overhead to "recurring overhead hours", reserve to "contingency %") and says nothing about people, days, or hoursPerDay, which are the three inputs that define gross capacity. The interaction between a percentage reserve and the hour-based inputs is also left unexplained.

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 precisely scoped resource, "sprint hours available for delivery," with the deduction order (absence, then recurring duties, then contingency). The scope is unambiguous, though the description makes no reference to any sibling utility, which is acceptable given the largely unrelated sibling set.

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 via the phrase "for delivery" and by the sprint-planning vocabulary, which makes the planning context clear without explicitly saying when to use this vs. a different forecasting tool. There are no exclusions, prerequisites, or named alternatives, and with no near-equivalent siblings that omission costs little.

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.