Skip to main content
Glama

Velocity Release Forecast

bpj_velocity_release_forecast
Read-onlyIdempotent

Use the last three completed iteration velocities to estimate remaining iterations at the mean and fastest observed pace.

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": {
      "scope": "<scope>",
      "v1": "<v1>",
      "v2": "<v2>",
      "v3": "<v3>"
    },
    "name": "bpj_velocity_release_forecast"
  }
}

Input Schema

NameRequiredDescriptionDefault
v1Yes
v2Yes
v3Yes
scopeYes

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 this a read-only, idempotent, closed-world, non-destructive tool, so the safety burden is off the description. The description does add the actual method — mean and fastest observed pace — which is genuine behavioral information. It omits what the output looks like (two estimates? in iterations?) and edge-case behavior when velocities are zero.

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 wasted wording; the inputs and the dual-pace output are stated immediately. It is efficient, though slightly terse for a tool whose result format is otherwise undocumented.

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?

This is a pure read-only computation with four simple numeric parameters and no output schema. The description covers the method but not the shape or units of the result, nor the two-pace output being returned as separate figures; for a calculation tool with no output schema, that leaves a real gap.

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 property titles ('Completed points three iterations ago', 'Last iteration completed points', 'Backlog points remaining') already convey each field's meaning. The description only loosely maps v1/v2/v3 to 'the last three completed iteration velocities' and does not specify ordering or units beyond what the titles give, so it adds marginal value rather than compensating for the formal 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 verb and computation: use three completed iteration velocities to 'estimate remaining iterations' at two paces. That is clearly distinguishable from the sibling release/packaging tools. It stops short of explicitly naming which sibling to use instead, so it lands at 4 rather than 5.

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?

Use is only implied by the phrase 'last three completed iteration velocities', which presupposes a completed-iteration context. There is no statement of when to prefer this over another forecast tool, no prerequisites (e.g., three completed iterations must exist), and no exclusion for zero-velocity or empty-backlog cases.

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.