Skip to main content
Glama

get_pending_estimates

Read-onlyIdempotent

Lists recent estimates that still need actual-hour feedback, helping you identify pending items and submit actuals through record_actual to close the estimation feedback loop.

Instructions

List recent estimates that have not yet received actual-hour feedback.

Returns estimates awaiting actuals so you can submit feedback via record_actual. Use this to close the estimation feedback loop and improve accuracy over time.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_pending_estimates"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax estimates to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.8.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, closed-world behavior, so the safety profile is covered. The description adds that results are the input to record_actual, which is useful workflow context, but says nothing about ordering, recency window, or what an empty result means.

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?

Three short, front-loaded sentences with the key filter stated first. The first two sentences overlap slightly ("have not yet received actual-hour feedback" vs "awaiting actuals"), a minor redundancy but not harmful.

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?

A simple, fully-annotated read tool with one documented parameter and no output schema; the description gives enough purpose and workflow linkage to call it correctly. Only the shape of returned estimate records is left implicit, which is acceptable given the tool's simplicity.

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 coverage is 100% for the single limit parameter (default 20, max 100), so the schema carries the semantics. The description adds no meaning about the limit or truncation behavior, which is the baseline-3 case for fully documented params.

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?

States a specific verb and resource (list estimates) plus the defining filter (not yet received actual-hour feedback), which separates it from sibling planning tools like record_actual and calibrate_estimates. An agent knows exactly what this returns 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?

Explicitly names the follow-up tool (record_actual) and the use case of closing the estimation feedback loop, so the agent knows what to do with results. It stops short of stating when not to use it or how it relates to the other pending-work siblings such as feedback_health.

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