Skip to main content
Glama

server

estimate_project

Read-onlyIdempotent

Use when a user or agent needs an indicative engineering timeline, starting price tier, and direct estimator URL for scoping a website, mobile app, custom software, or AI automation project.

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_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
scaleNoProject complexity tier: 'starter' (1-3 weeks), 'growth' (4-6 weeks), or 'comprehensive' (6-12 weeks).growth
serviceSlugNoOptional canonical service slug such as 'websites', 'applications', 'custom-software', or 'ai-automation'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 without the description. The description does add that the result is an estimate ("indicative", "starting price tier") rather than a firm quote, and that it returns a direct estimator URL, which is useful context. It does not explain how the returned values vary with scale or what the estimator link points to, leaving some behavioral detail unstated.

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?

A single sentence front-loaded with "Use when..." and then the output payload and supported project types. Every clause carries information; only the trailing domain list could be trimmed, and even that clarifies scope.

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 two-optional-parameter, read-only lookup with a fully described schema, rich annotations, and no output schema, the description supplies the trigger condition, the returned artifacts, and the supported project categories. The remaining gap is guidance on how this relates to get_services (e.g. fetching the service catalog first), which would make it self-sufficient.

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%: both `scale` (with per-enum week ranges) and `serviceSlug` (with example slugs) are fully documented in the schema. The description adds nothing about either parameter, so the baseline 3 applies — the schema carries the full burden and does it well.

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 names a concrete outcome set — indicative engineering timeline, starting price tier, and a direct estimator URL — plus the project domains it covers (website, mobile app, custom software, AI automation). That is far more specific than the tool name alone. It stops short of explicitly distinguishing itself from get_services or get_case_studies, but the estimating/scoping framing is distinct enough to route correctly.

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?

"Use when a user or agent needs an indicative engineering timeline, starting price tier, and direct estimator URL for scoping..." gives a clear trigger condition. There is no explicit when-not-to-use guidance and no reference to sibling tools such as get_services for a full catalog lookup, so the routing is implied rather than 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.

Resources