Skip to main content
Glama

Pumpkin

check_service_area

Read-only

Check whether a city or postal code is explicitly served. Include the region when known.

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>"
    },
    "name": "check_service_area"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo
siteYesThe site ID returned by find_business.
regionNo
postalCodeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already establish readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds useful nuance that the check is for explicitly served areas and that the region should be included when known, but it does not disclose the return format or what happens when an area is not served.

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 short sentences, front-loaded with the purpose and followed by a compact parameter note. There is no redundant wording or repeated schema content.

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?

The tool is a simple read-only check and the annotations cover its safety profile. However, there is no output schema and the description does not explain the return values or the next step when the area is not served, which is a meaningful gap for an agent invoking it.

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 only 25%, with just the required site parameter documented. The description partially compensates by naming city and postalCode as accepted inputs and explaining that region should be included when known, but it leaves the relationship between city and postalCode and the full role of site unclear.

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 specific verb ('Check') and resource ('whether a city or postal code is explicitly served'), so the core purpose is clear. It does not differentiate this tool from siblings such as service_estimate or service_windows, and 'explicitly served' is not fully explained.

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?

There is no explicit when-to-use or when-not guidance, and no alternative tool is named. 'Include the region when known' is parameter guidance rather than guidance on choosing this tool over service_estimate or service_windows.

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