Skip to main content
Glama

PERT Three-Point Estimate

bpj_pert_estimate
Read-onlyIdempotent

Calculate the PERT weighted duration and spread from optimistic, most likely, and pessimistic durations.

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": {
      "optimistic": "<optimistic>",
      "likely": "<likely>",
      "pessimistic": "<pessimistic>"
    },
    "name": "bpj_pert_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
likelyYes
optimisticYes
pessimisticYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior, so the description needn't carry the safety profile. The description adds that it computes a weighted duration and a spread, which is useful output context, but does not specify the PERT formula, what 'spread' means (standard deviation vs. variance), or units of the return values.

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 with no filler. Every phrase contributes: the verb, the computed quantities, and the three inputs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple three-parameter calculator whose annotations cover safety and determinism, the description is mostly complete: it names inputs and the conceptual outputs. It could be stronger by clarifying the exact return values or formula variant, but nothing essential for correct invocation is missing.

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%, and the schema only provides titles. The description compensates by mapping the three numeric parameters to optimistic, most likely, and pessimistic durations, which is meaningful. However, it does not add units, expected scale, or whether the estimates must be ordered (optimistic <= likely <= pessimistic), leaving some semantic gaps.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Calculate') with a clearly named resource ('PERT weighted duration and spread') and names the exact inputs. An agent can immediately distinguish this from unrelated calculator siblings like break-even or cash-runway tools.

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 implied by the tool's self-contained nature: call it when you have three duration estimates and need a PERT result. There is no explicit when-to-use or when-not-to-use guidance, and no alternatives are named, but for a pure calculator with no apparent sibling overlap this is minimally adequate.

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.