Skip to main content
Glama

Find areas

list_areas
Read-onlyIdempotent

List supported areas

Cities, neighborhoods and states Atly covers — densest in the United States, with pockets in Mexico, Israel and Thailand — each with an id you can pass to search, a center, a bounding box when known, and how many places it holds. Filter with q (substring of the name) and level (city, neighborhood, state). Results are ordered by place count.

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_areas"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoArea name or common abbreviation, e.g. "san diego", "midtown", "nyc". Exact and prefix matches rank first.
levelNoRestrict to one level.
limitNoMaximum areas to return, at most 200; a larger value returns 200.

Output Schema

NameRequiredDescriptionDefault
areasNo
totalNo
call_idNo
doc_notesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / limit / maximum
      Added value: +9007199254740991
    • changedOutput schema / additionalProperties
      Previous value: -falseNew value: +{}
    • changedOutput schema / properties / areas / anyOf
      Previous value: -[
      -  {
      -    "items": {
      -      "additionalProperties": false,
      -      "properties": {
      -        "bbox": {
      -          "anyOf": [
      -            {
      -              "description": "[west, south, east, north]",
      -              "items": {
      -                "type": "number"
      -              },
      -              "type": "array"
      -            },
      -            {
      -              "type": "null"
      -            }
      -          ],
      -          "description": "[west, south, east, north]"
      -        },
      -        "center": {
      -          "anyOf": [
      -            {
      -              "description": "[lon, lat]",
      -              "items": {
      -                "type": "number"
      -              },
      -              "type": "array"
      -            },
      -            {
      -              "type": "null"
      -            }
      -          ],
      -          "description": "[lon, lat]"
      -        },
      -        "country": {
      -          "description": "Country the area is in. Coverage is densest in the United States",
      -          "type": [
      -            "string",
      -            "null"
      -          ]
      -        },
      -        "id": {
      -          "type": [
      -            "string",
      -            "null"
      -          ]
      -        },
      -        "level": {
      -          "type": [
      -            "string",
      -            "null"
      -          ]
      -        },
      -        "name": {
      -          "type": [
      -            "string",
      -            "null"
      -          ]
      -        },
      -        "parent": {
      -          "description": "City for neighborhoods.",
      -          "type": [
      -            "string",
      -            "null"
      -          ]
      -        },
      -        "place_count": {
      -          "anyOf": [
      -            {
      -              "type": "integer"
      -            },
      -            {
      -              "type": "null"
      -            }
      -          ]
      -        },
      -        "region": {
      -          "description": "State for US cities and neighborhoods; the equivalent district or province elsewhere.",
      -          "type": [
      -            "string",
      -            "null"
      -          ]
      -        }
      -      },
      -      "type": "object"
      -    },
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "items": {
      +      "additionalProperties": {},
      +      "properties": {
      +        "bbox": {
      +          "anyOf": [
      +            {
      +              "items": {
      +                "type": "number"
      +              },
      +              "type": "array"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "description": "[west, south, east, north]"
      +        },
      +        "center": {
      +          "anyOf": [
      +            {
      +              "items": {
      +                "type": "number"
      +              },
      +              "type": "array"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "description": "[lon, lat]"
      +        },
      +        "country": {
      +          "anyOf": [
      +            {
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "description": "Country the area is in. Coverage is densest in the United States, with pockets in Mexico, Israel and Thailand."
      +        },
      +        "id": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "level": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "name": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "parent": {
      +          "anyOf": [
      +            {
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "description": "City for neighborhoods."
      +        },
      +        "place_count": {
      +          "anyOf": [
      +            {
      +              "maximum": 9007199254740991,
      +              "minimum": -9007199254740991,
      +              "type": "integer"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ]
      +        },
      +        "region": {
      +          "anyOf": [
      +            {
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "description": "State for US cities and neighborhoods; the equivalent district or province elsewhere."
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedOutput schema / properties / total / anyOf
      Previous value: -[
      -  {
      -    "type": "integer"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "maximum": 9007199254740991,
      +    "minimum": -9007199254740991,
      +    "type": "integer"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. Changed2 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Maximum areas to return, at most 200; a larger value returns 200."
    • removedInput schema / properties / limit / maximum
      Removed value: -200
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, and the description adds useful context beyond them: geographic coverage, area attributes, filterable levels, and result ordering. It does not mention auth or rate limits, but the annotations carry the safety profile and the description enriches the operational picture.

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?

The opening sentence front-loads the purpose, and subsequent details about coverage, returned fields, filtering, and ordering are useful. The geographic aside is slightly verbose but not wasteful for a discovery tool.

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 an output schema present, the description need not explain return values, but it does clarify area attributes and ordering. It also covers filtering behavior and scope, leaving only explicit sibling-comparison guidance as a minor gap.

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 the schema already documents `q`, `level`, and `limit`. The description adds some meaning by calling `q` a substring filter and restating the allowed `level` values, but it does not mention `limit` and largely repeats schema-level details, matching the baseline for high schema coverage.

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 states a specific verb and resource ('List supported areas') and clarifies the domain with geographic coverage and returned fields. It is clearly distinguishable from a generic search tool, though it does not explicitly contrast itself with siblings like search_places or list_categories.

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?

It explains how to filter with `q` and `level` and notes that area IDs can be passed to search, implying downstream use. However, it gives no explicit when-to-use guidance relative to alternatives such as search_places or list_categories, so the agent must infer the selection criteria.

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.