Skip to main content
Glama

Cost Performance Completion Forecast

bpj_cost_performance_completion_forecast
Read-onlyIdempotent

Project final cost assuming the remaining work continues at the cumulative cost performance index.

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": {
      "budget": "<budget>",
      "earned": "<earned>",
      "actual": "<actual>"
    },
    "name": "bpj_cost_performance_completion_forecast"
  }
}

Input Schema

NameRequiredDescriptionDefault
actualYes
budgetYes
earnedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, closed-world, and non-destructive, so the safety profile is covered. Beyond that, the description discloses the actual computational model (forward projection of remaining work at the cumulative CPI), which is genuine behavioral content an agent would not get from the structured fields. It omits edge-case behavior such as division-by-zero when actual or earned is zero, and the return shape, which keeps it out of the top score.

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 that states the computed quantity and its assumption with no filler. Nothing could be removed without losing meaning.

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 calculation tool with no output schema, the description gives the method but not the input-to-output mapping or edge-case handling. An agent knows what the tool conceptually does but not precisely how the three required numbers are combined into 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 the description contributes no parameter meaning at all: it never states that budget maps to BAC, earned to EV, actual to AC, or that CPI is derived as earned divided by actual. The only aid is the schema's own titles, so the description fails to compensate for the coverage gap on a formula whose correctness depends on the input relationship.

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 computation (project the final cost) and its governing assumption (remaining work at the cumulative CPI), which is far more than a restatement of the title. It does not, however, distinguish itself from the closely related sibling bpj_to_complete_performance_index, which an agent could easily confuse with this EAC-style forecast.

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 explicit when-to-use, when-not-to-use, or alternative-naming guidance. The scenario is only implied by the CPI language, and nothing tells the agent how this differs from TCPI or the other forecast siblings, so selection between them is left to inference.

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.