Skip to main content
Glama

Pumpkin

service_estimate

Read-only

Estimate a selected service from an explicit quantity. Staff must confirm.

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": {
      "site": "<site>",
      "itemId": "<itemId>",
      "quantity": "<quantity>"
    },
    "name": "service_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesThe site ID returned by find_business.
itemIdYes
quantityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is known. The description adds one genuinely useful trait beyond that — the estimate is not authoritative and requires staff confirmation — but says nothing about pricing basis, failure modes for unavailable services, or whether repeated calls can differ.

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 with no filler; the core operation is front-loaded and the caveat follows. Slightly under-specified rather than verbose, but nothing is wasted.

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 three required parameters, no output schema, and no enums, the description should do more — particularly on what the estimate returns and where itemId comes from. It conveys the essential operation and the confirmation caveat, but leaves the discovery-to-estimate workflow implicit.

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 only 33%: site is documented in the schema as coming from find_business, but itemId has no description in either place. 'Selected service' weakly implies itemId comes from a prior search/selection step, and 'explicit quantity' stresses that quantity is not inferred, but itemId's provenance and format remain unexplained.

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 specific verb ('Estimate') and resource ('a selected service') plus the driving input ('an explicit quantity'), so the operation is identifiable. It does not distinguish this from rental_estimate or explain the relationship to service_search/service_get, so an agent must infer those boundaries from names alone.

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?

'Staff must confirm' hints this is a preliminary, non-binding figure rather than a commitment, which implies it precedes service_request_prepare/submit. However, no explicit when-to-use/when-not guidance or named alternative (e.g. rental_estimate for rentals) is given.

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