Skip to main content
Glama

estimate_ai_service

Read-onlyIdempotent

Estimate AI service costs, retainer, setup fee, overages and margin in USD. User-supplied model rates. No data saved or purchases made.

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": "estimate_ai_service"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNo
scopeNo
titleNo
agencyNo
clientNo
hourlyCostNoYour delivery cost ($ / hour)
inputPriceNoInput price ($ / million tokens)
setupHoursNoSetup + implementation hours
inputTokensNoInput tokens / model call
outputPriceNoOutput price ($ / million tokens)
outputTokensNoOutput tokens / model call
platformCostNoHosting + tools ($ / month)
supportHoursNoSupport hours / month
marginPercentNoTarget gross margin (%)
callsPerRequestNoModel calls / request
monthlyRequestsNoClient requests / month
contingencyPercentNoCost contingency (%)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 fully covered. The description's 'No data saved or purchases made' restates that, but 'User-supplied model rates' adds genuinely non-obvious behavior: no external price fetching occurs. It stops short of describing the output breakdown or whether retainer/overage math is disclosed.

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 terse sentences, front-loaded with the purpose and closed with the critical safety caveat. No filler, no restatement of the name.

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?

For a 17-parameter estimation tool with no output schema, the description should say what the estimate returns (a line-item breakdown? a single total?) and how retainer, overage and margin interact. It covers the cost components but leaves the response shape and the role of the five string fields unaddressed.

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 71%, above the low-coverage threshold, and the numeric parameters already carry dollar-unit descriptions. The description adds little beyond the schema, and the five undocumented string parameters (model, scope, title, agency, client) are never explained — an agent must guess whether they are labels, metadata, or model identifiers.

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 opens with a concrete verb+resource ('Estimate AI service costs') and enumerates the specific components being priced: retainer, setup fee, overages and margin, in USD. It is unambiguous what the tool produces. No sibling tools exist, so sibling differentiation cannot be earned.

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?

The phrase 'User-supplied model rates' plus 'No data saved or purchases made' implies this is for what-if pricing rather than live billing lookups, which is useful routing context. However, no explicit when-to-use or when-not-to-use guidance is given, and no prerequisites (e.g., 'requires rates from your provider') are stated.

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.