Skip to main content
Glama

List service areas

list_service_areas
Read-onlyIdempotent

Cities with currency, timezone, radius and tier. tier is driver presence, not whether booking works: "live" = drivers based there were online in the last 24 h; "scheduled" = bookable, approved drivers are based there (book ahead, we match one); "waitlist" = not bookable yet. Never call a scheduled city unavailable or not live; say it is bookable ahead. Free.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: the precise meaning of each tier value, the driver-presence semantics behind 'live', and the fact that the call is free. It does not mention caching or freshness of driver-presence data, which is the one remaining behavioral gap.

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?

It is front-loaded with the returned fields, then drills into the only non-obvious attribute, tier. The tier explanation is slightly circular ('bookable ahead, we match one' / 'say it is bookable ahead') but every sentence carries semantic weight for an agent that must report results.

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?

With no output schema, the description reasonably enumerates the returned fields and fully explains the one ambiguous enum-like value. A delivery or coverage agent has enough to both call it and phrase its results correctly; the only shortfall is not describing the overall response shape (array vs object) or ordering.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly spends no words on inputs.

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 opening clause names the resource and its returned attributes (cities with currency, timezone, radius, tier), making the tool's output identifiable at a glance. It does not distinguish itself from check_coverage or list_country_workspaces, so the sibling differentiation piece is missing.

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 guidance is embedded as interpretation rules for the three tier values and an explicit 'never call a scheduled city unavailable' prohibition, plus a 'Free' cost note. It never states when to call this versus check_coverage, which is the closest sibling, so the alternative-selection guidance is implied at best.

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.