Skip to main content
Glama

Check service area by ZIP

check_service_area
Read-onlyIdempotent

Check whether AtlantFlow serves a location. Returns status 'served' (primary service area), 'ask' (listed or nearby but availability must be confirmed by phone) or 'not_served' (outside Palm Beach, Broward and Miami-Dade). Give a ZIP whenever possible.

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

Input Schema

NameRequiredDescriptionDefault
zipNo5-digit US ZIP code of the property, e.g. '33487'. Preferred - gives a definite answer.
cityNoCity name, e.g. 'Delray Beach'. Used when no ZIP is known.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/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 covered. The description adds genuinely new behavioral context: the three possible outcomes and what each means operationally (primary area vs. phone-confirm vs. out of area). It does not cover edge cases like supplying neither ZIP nor city, but that is minor.

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?

Three tight sentences, front-loaded with purpose, then outcomes, then the input preference. Every sentence carries information, though the status enumeration could be compressed slightly without loss.

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?

There is no output schema, so the description correctly carries the burden of explaining return values, which it does thoroughly via the three statuses. For a 2-optional-parameter read-only lookup it is nearly complete; only the behavior when neither parameter is supplied is unstated.

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%, so both zip and city already carry examples and usage notes. The description reinforces the ZIP-over-city preference, which slightly exceeds the schema but adds no new semantics beyond it. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Check whether AtlantFlow serves a location') plus the exact domain (Palm Beach, Broward, Miami-Dade). The enumerated return states make it immediately distinguishable from siblings like request_service or get_company_info.

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 final sentence 'Give a ZIP whenever possible' gives clear preference guidance for inputs, and the 'ask' status hints that phone confirmation may follow. However, there is no explicit statement of when to call this versus alternatives such as request_service, and no in/out-of-scope exclusion beyond geography.

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