Skip to main content
Glama

To-Complete Performance Index

bpj_to_complete_performance_index
Read-onlyIdempotent

Calculate the cost efficiency needed on unfinished budgeted work to meet a target final cost.

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>",
      "target": "<target>"
    },
    "name": "bpj_to_complete_performance_index"
  }
}

Input Schema

NameRequiredDescriptionDefault
actualYes
budgetYes
earnedYes
targetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare this read-only, idempotent and non-destructive, so the safety profile is covered. Beyond that, the description adds almost nothing behavioral: it does not disclose the underlying formula, the units of the result, or the edge case where target is less than actual cost (which drives the denominator to zero or negative). For a pure computation tool with no output schema, that omission is material.

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 compact sentence with the key concept front-loaded and no filler. It is efficient, though the brevity is achieved by omitting the operational detail the tool actually needs.

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?

With four required numeric parameters, no output schema, and no formula or result interpretation, the description is too thin for the tool's complexity. An agent knows the general intent but not how the inputs combine, what the returned index means, or what constitutes an invalid call. It would likely need a second source of information to invoke this correctly.

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 schema offers only titles for the four numeric fields, so the description carries the full burden. It gestures at budget, earned value, actual cost and target, but never maps them to the inputs or states the relationship (e.g. that budget minus earned is the numerator and target minus actual the denominator). An agent cannot tell from the description how 'target' differs from 'budget'.

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 uses a specific verb ('Calculate') and names the resource precisely: the cost efficiency required on unfinished budgeted work to hit a target final cost. That is a recognizable TCPI definition an agent can match to a request. It does not, however, distinguish itself from the sibling bpj_cost_performance_completion_forecast, which also deals with cost-to-completion, so the boundary between the two must be inferred.

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 call this versus the cost-forecast sibling, no prerequisites, and no note on when the calculation is meaningless. An agent must already know earned-value management conventions to know this applies only when a target final cost is imposed. No alternatives or exclusions are stated.

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.