Skip to main content
Glama

Scope Change Schedule Impact

bpj_scope_change_schedule_impact
Read-onlyIdempotent

Translate a net change of scope hours into revised effort and delivery days at fixed team capacity.

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": {
      "baseline": "<baseline>",
      "changed": "<changed>",
      "capacity": "<capacity>"
    },
    "name": "bpj_scope_change_schedule_impact"
  }
}

Input Schema

NameRequiredDescriptionDefault
changedYes
baselineYes
capacityYes

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 establish readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile needs no restatement. The description adds one genuinely useful behavioral constraint, that the calculation assumes fixed team capacity, but says nothing about sign handling for scope reductions, rounding, or what 'revised effort' means numerically.

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 well-formed sentence that front-loads the input and output quantities with no filler. It is efficient, though its brevity is also the source of the missing edge-case detail.

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-parameter numeric calculation with no output schema, the description covers the shape of the transformation but not the mechanics. It does not state the arithmetic relationship, how fractional days are treated, or how a zero/negative resulting effort would be reported, which an agent needs to trust the result.

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 coverage is 0%, so the burden falls on the description, which partly delivers: it names the net scope change and the capacity driver. However, the baseline parameter is only indirectly implied by 'revised effort', and nothing explains that 'changed' may be negative (the schema allows down to -1e10) to model descoping.

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 clear verb ('translate') plus the input and output quantities: net scope hours in, revised effort and delivery days out. That is specific enough to distinguish it from calculation siblings like bpj_schedule_crash_cost_slope or bpj_schedule_critical_path, though it never explicitly contrasts itself with them.

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 guidance, no stated preconditions, and no named alternative. The clause 'at fixed team capacity' implies a constraint on applicability, but the agent is left to infer when this model is appropriate versus a reallocation or critical-path tool.

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.