Skip to main content
Glama

estimate_ai_project_cost

Read-onlyIdempotent

Use when planning the budget for an AI proof of concept, pilot or production workflow. Returns an editable team-and-duration cost range with explicit assumptions, not a quote.

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": {
      "stage": "<stage>"
    },
    "name": "estimate_ai_project_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
stageYes
peopleNo
dayRateNo
currencyNo
durationWeeksNo

Output Schema

NameRequiredDescriptionDefault
resultYes
generatorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already establish this as a read-only, idempotent, closed-world, non-destructive operation, so safety is covered. The description adds genuinely new behavioral context by characterizing the output as an editable range with explicit assumptions rather than a firm quote. It says nothing, however, about how user-supplied people/dayRate/durationWeeks interact with the estimate versus defaults.

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?

Two sentences, no filler, with the usage trigger front-loaded and the output characterization second. Every clause carries information the agent cannot get from the schema or annotations.

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?

With rich annotations and an output schema, the description only needs to cover purpose and parameter intent, and it covers purpose well. The gap is parameter grounding: for a 5-parameter tool at 0% schema coverage, the agent still does not know what stage selects or how dayRate/currency/durationWeeks shape the result.

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 parameter meaning, and it only partially does: 'team-and-duration' hints at people and durationWeeks. The stage enum, dayRate, and currency (a strict ISO-4217 pattern) receive no explanation of their role or defaults, leaving the agent to infer.

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?

The description gives a concrete outcome: it returns an 'editable team-and-duration cost range with explicit assumptions, not a quote,' which tells the agent exactly what kind of artifact to expect. It stops short of distinguishing itself from the sibling estimate_ai_roi, which is a closely related estimation tool an agent could easily confuse it with.

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?

The opening clause 'Use when planning the budget for an AI proof of concept, pilot or production workflow' gives a clear triggering context and implicitly ties to the stage values. It never states when not to use it or names the ROI-estimation sibling as the alternative for return-on-investment questions.

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.