Skip to main content
Glama

Estimate a project cost range

estimate_project
Read-onlyIdempotent

Estimate the cost range for a specific software project. Uses the same calculation as the estimator on the website, so the answer matches what a person would be shown.

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": {
      "projectType": "<projectType>"
    },
    "name": "estimate_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
scaleNoRoughly how many people will use it?
audienceNoWho will use it?
timelineNoWhen does it need to be live?
projectTypeYesWhat are you building?
integrationsNoWhat does it need to talk to?
newOrReplacementNoIs this new, or replacing something?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / projectType / enum
      Previous value: -[
      -  "booking",
      -  "portal",
      -  "webApp",
      -  "aiAutomation",
      -  "headlessCms",
      -  "platform",
      -  "integration",
      -  "integrationLayer",
      -  "takeOver",
      -  "ongoingSupport",
      -  "website",
      -  "store",
      -  "notSure"
      -]New value: +[
      +  "booking",
      +  "portal",
      +  "webApp",
      +  "aiAutomation",
      +  "headlessCms",
      +  "internalTools",
      +  "integration",
      +  "integrationLayer",
      +  "takeOver",
      +  "ongoingSupport",
      +  "website",
      +  "store",
      +  "notSure"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / projectType / enum
      Previous value: -[
      -  "booking",
      -  "portal",
      -  "webApp",
      -  "aiAutomation",
      -  "headlessCms",
      -  "platform",
      -  "integration",
      -  "integrationLayer",
      -  "takeOver",
      -  "ongoingSupport",
      -  "notSure"
      -]New value: +[
      +  "booking",
      +  "portal",
      +  "webApp",
      +  "aiAutomation",
      +  "headlessCms",
      +  "platform",
      +  "integration",
      +  "integrationLayer",
      +  "takeOver",
      +  "ongoingSupport",
      +  "website",
      +  "store",
      +  "notSure"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / projectType / enum
      Previous value: -[
      -  "booking",
      -  "portal",
      -  "webApp",
      -  "aiAutomation",
      -  "headlessCms",
      -  "platform",
      -  "integration",
      -  "integrationLayer",
      -  "notSure"
      -]New value: +[
      +  "booking",
      +  "portal",
      +  "webApp",
      +  "aiAutomation",
      +  "headlessCms",
      +  "platform",
      +  "integration",
      +  "integrationLayer",
      +  "takeOver",
      +  "ongoingSupport",
      +  "notSure"
      +]
  4. Changed1 schema field changed
    • changedInput schema / properties / projectType / enum
      Previous value: -[
      -  "booking",
      -  "portal",
      -  "webApp",
      -  "aiAutomation",
      -  "headlessCms",
      -  "platform",
      -  "notSure"
      -]New value: +[
      +  "booking",
      +  "portal",
      +  "webApp",
      +  "aiAutomation",
      +  "headlessCms",
      +  "platform",
      +  "integration",
      +  "integrationLayer",
      +  "notSure"
      +]
  5. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior. The description adds one genuinely useful behavioral fact — that results match the public website estimator, so figures are consistent with what a human would see — but it says nothing about rate limits, latency, or what the returned range actually contains, which matters because there is no output schema.

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?

Two short sentences, front-loaded with the core action. The second sentence about matching the website estimator is not wasteful, but the wording is slightly promotional rather than operational.

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?

Parameters are fully covered by the schema, but with no output schema the description should describe what comes back — a currency-formatted range, an object, a disclaimer. It only says 'cost range,' leaving the return shape to inference on a 6-parameter tool.

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%: every parameter, including all five enums, is documented with a plain-language question in the schema. The description adds no extra meaning about parameter interactions or which inputs most affect the estimate, so the baseline of 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 clear verb and resource: estimate the cost range for a specific software project. It does not distinguish itself from the related sibling get_pricing_and_services, so an agent cannot tell from the description alone which of the two to reach for.

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?

The description gives no when-to-use or when-not-to-use guidance and names no alternatives. It implies the tool estimates project cost but never says how that differs from fetching pricing or services via the sibling tools.

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