Skip to main content
Glama

Earned Value Analysis

bpj_earned_value
Read-onlyIdempotent

Calculate schedule and cost variance and performance indices from planned value, earned value, and actual 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": {
      "planned": "<planned>",
      "earned": "<earned>",
      "actual": "<actual>"
    },
    "name": "bpj_earned_value"
  }
}

Input Schema

NameRequiredDescriptionDefault
actualYes
earnedYes
plannedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this is a read-only, idempotent, closed-world, non-destructive calculation, so the safety profile needs no restating. The description adds genuinely new context by naming the outputs produced (schedule variance, cost variance, performance indices), which matters because there is no output schema. It does not disclose the exact formulas or units, keeping it off a 5.

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?

One sentence, front-loaded with the verb and outcome, with zero filler or redundancy. Every clause carries information: the metrics computed and the inputs consumed.

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-number pure-calculation tool this is close to adequate, and with no output schema the description at least names the result categories. Gaps remain: which indices (SPI/CPI), the exact return fields, and unit conventions are unstated, so an agent cannot fully predict the response shape.

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%, so the description must carry the weight, and it does expand the acronym semantics by tying 'planned value', 'earned value', and 'actual cost' to the three required properties. However, it adds no unit/currency guidance and does not say whether values are cumulative or period-based, leaving real ambiguity in a 0%-coverage schema.

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 ('Calculate') and a specific resource ('schedule and cost variance and performance indices'), plus the three inputs it consumes. An agent immediately knows this is an earned-value-metrics computation, distinct from the finance tools in the sibling list such as bpj_cash_runway or bpj_break_even_units. It stops short of naming any sibling to contrast with.

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: the description tells you the tool needs planned, earned, and actual values, which signals when it applies (project cost/schedule tracking). There is no explicit when-to-use or when-not-to-use statement, and no prerequisites such as 'inputs must be cumulative to the same status date'.

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.