Skip to main content
Glama

pert_estimate

Read-onlyIdempotent

Calculates PERT expected duration from optimistic, most-likely, and pessimistic estimates, returning variance, standard deviation, and 95%/99% confidence bounds to support uncertain task duration planning.

Instructions

Calculate PERT expected duration from three-point estimates using Beta distribution.

Formula: E = (O + 4M + P) / 6. Returns expected value, variance, standard deviation, and 95%/99% confidence bounds with urgency categorization. Use when estimating task duration with uncertain outcomes.

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>",
      "most_likely": "<most_likely>",
      "pessimistic": "<pessimistic>"
    },
    "name": "pert_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitNoTime unit for all three PERT estimates.hours
projectNoOptional project/repo identifier this estimate belongs to, for cross-project analytics.
ai_nativeNoDegree of AI assistance: 0.0 = fully human, 1.0 = fully AI-native, 0.5 = hybrid. Accepts boolean for backward compatibility (true=1.0, false=0.0).
task_typeNoOptional task type for feedback matching. Enables per-task-type accuracy tracking.
complexityNoOptional complexity hint from 1 (trivial) to 5 (extreme). Reserved for future per-complexity correction-factor conditioning; not yet applied to the headline estimate.
optimisticYesBest-case duration. Do NOT use your initial optimistic guess — this should be the absolute minimum if everything goes perfectly.
session_idNoOptional session identifier (minted by a calling agent/hook) used to deduplicate repeated estimate calls for the same task within a session.
task_labelNoOptional free-text label identifying the task this estimate is for (e.g. an issue key or short title). Surfaced on get_pending_estimates output for triage.
most_likelyYesMode of the distribution — the single most probable outcome.
pessimisticYesWorst-case duration accounting for known risks and unknown unknowns.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.8.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / ai_native / default
      Removed value: -1
    • addedInput schema / properties / complexity
      Added value: +{
      +  "description": "Optional complexity hint from 1 (trivial) to 5 (extreme). Reserved for future per-complexity correction-factor conditioning; not yet applied to the headline estimate.",
      +  "maximum": 5,
      +  "minimum": 1,
      +  "type": "number"
      +}
    • addedInput schema / properties / project
      Added value: +{
      +  "description": "Optional project/repo identifier this estimate belongs to, for cross-project analytics.",
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / session_id
      Added value: +{
      +  "description": "Optional session identifier (minted by a calling agent/hook) used to deduplicate repeated estimate calls for the same task within a session.",
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / task_label
      Added value: +{
      +  "description": "Optional free-text label identifying the task this estimate is for (e.g. an issue key or short title). Surfaced on get_pending_estimates output for triage.",
      +  "minLength": 1,
      +  "type": "string"
      +}
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is clear. Beyond that, the description discloses the calculation formula and the specific outputs: expected value, variance, standard deviation, confidence bounds, and urgency categorization. It doesn't explain how urgency categories are assigned, but the added behavioral detail is substantial.

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?

The description is front-loaded with the main purpose, then provides the formula, output details, and usage guidance in four efficient lines. Every sentence contributes materially, and there is no redundant or filler text.

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?

There is no output schema, so the description usefully enumerates the return values and includes the calculation formula. It omits detail about optional analytics parameters and how urgency categorization is computed, but the core invocation is fully explained. Given the 10-parameter schema with 100% coverage, the description is nearly complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all parameters thoroughly. The description adds conceptual meaning by mapping the three-point inputs to the formula variables O, M, and P, and by framing the distribution as Beta. It does not detail optional parameters like project or task_type, but their schema descriptions are sufficient.

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 states a specific verb and resource: calculate PERT expected duration from three-point estimates using a Beta distribution. It names the formula and return components, which distinguishes it from sibling estimators like cocomo_estimate or monte_carlo_schedule. An agent can identify the tool's exact operation without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear usage context: 'Use when estimating task duration with uncertain outcomes.' This narrows the use case effectively. However, it does not explicitly name when not to use it or direct the agent to an alternative sibling for related estimation scenarios.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.