Skip to main content
Glama

Check the service area

check_service_area
Read-only

Is a ZIP code in Ryan's service area? He covers Temecula, Murrieta, Menifee, Wildomar, French Valley, Winchester.

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

Input Schema

NameRequiredDescriptionDefault
zipYes5-digit ZIP of where the car will be.

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 and openWorldHint=false, so safety is covered. The description adds one genuine behavioral fact beyond the annotations: coverage is a fixed named-city list rather than a radius or drive-time calculation. It does not say what is returned (boolean vs. list of nearest covered cities) or how adjacent-but-unlisted ZIPs are handled.

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 question and followed by the coverage list; nothing is padded. The second sentence is a fragment, which reads efficiently but makes the coverage list slightly ambiguous as to its role.

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?

For a one-parameter read with no output schema, an agent would benefit from knowing the return shape and boundary behavior (out-of-area but adjacent ZIPs, prefix matching). The description leaves return semantics entirely implicit, though the questioning phrasing strongly hints at a yes/no result.

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 100% with a pattern-constrained 5-digit ZIP, so the schema carries the parameter burden. The description adds no format, canonicalization, or edge-case guidance (e.g., leading zeros, ZIP+4) beyond restating that a ZIP is expected.

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?

Names a specific check (ZIP-in-service-area) and immediately disambiguates what 'service area' means by listing the covered cities. The named geography lets an agent distinguish this from any radius- or region-based lookup without opening the schema.

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?

Usage is only implied by the tool's narrow question form — an agent can infer it is a pre-booking coverage gate. There is no explicit statement of when to call it, no prerequisite, and no mention of related tools such as get_quote or request_booking where coverage would matter.

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