Skip to main content
Glama

schedule_risk

Read-onlyIdempotent

Assess schedule risk for an effort estimate using historical accuracy data, returning confidence intervals, a risk level, and actionable recommendations.

Instructions

Assess schedule risk for an estimate using historical accuracy data.

Computes confidence intervals (p50/p80/p90/p95) based on your team's MAPE. Returns risk level and actionable recommendations. Uses industry baseline (25% MAPE) when no historical data is available.

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": {
      "estimated_hours": "<estimated_hours>"
    },
    "name": "schedule_risk"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectNoOptional project/repo identifier this estimate belongs to, for cross-project analytics.
team_idNoOptional team identifier to scope historical data.
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 to refine historical accuracy lookup.
complexityNoTask complexity from 1 (trivial) to 5 (extreme). Higher complexity widens confidence intervals.
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.
estimated_hoursYesThe estimated effort in hours to assess risk for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.8.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / ai_native / default
      Removed value: -1
    • 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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: it discloses the exact output shape (p50/p80/p90/p95 confidence intervals plus risk level and recommendations) and the 25% MAPE industry fallback when history is missing. It still says nothing about latency, cost, or how thin a history must be to trigger the fallback.

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?

Four short lines, front-loaded with the purpose, then output shape, then the fallback rule. No sentence is filler and nothing is repeated from the schema.

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 read-only, non-destructive scoring tool with 8 fully documented parameters and no output schema, the description covers purpose, return values, and the key fallback condition. Minor gaps remain around what 'risk level' categories mean and whether results depend on team_id scope, but an agent has enough to call it correctly.

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 100%, so the schema already documents all eight parameters, including the ai_native 0-1 scale and complexity's interval-widening effect. The description's mention of 'your team's MAPE' loosely connects to team_id and complexity but adds no syntax, defaults, or interaction detail beyond the schema; baseline 3 applies.

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 and resource ('Assess schedule risk for an estimate') plus the data source ('historical accuracy data'). An agent can tell it is a risk-scoring tool rather than an estimator, but the description never names or contrasts it with close siblings such as monte_carlo_schedule or reference_class_estimate.

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 or when-not-to-use guidance and no alternative named. The only conditional statement ('Uses industry baseline (25% MAPE) when no historical data is available') describes internal fallback behavior, not tool selection, so the agent must infer positioning against the many sibling estimation tools.

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