Skip to main content
Glama

Evendo Places

List areas inside a place

list_subareas
Read-only

List the direct children of a place, e.g. the neighbourhoods of a city or the cities of a region, most prominent first. Useful to suggest areas to explore or to narrow a search.

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": {
      "place_id": "<place_id>"
    },
    "name": "list_subareas"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNo
place_idYesID from resolve_place.
area_typeNoe.g. Neighbourhoods for a city, Cities for a region, CountryRegions for a country. Omit to see everything one level down, which can include featured venues, not just areas.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuine behavioral context — results are 'direct children' returned 'most prominent first' — but says nothing about pagination despite limit/cursor parameters, and the caveat that omitting area_type can return featured venues lives only in the schema, not here.

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 scope-defining clause and followed by the use case. No filler and no repetition of the title.

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 simple read-only listing tool the core semantics are adequately conveyed, and the absence of an output schema does not obligate it to explain returns. However, with 50% parameter coverage and undocumented limit/cursor, an agent gets no guidance on result volume or how to page through children.

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 description's examples map directly onto area_type values ('neighbourhoods of a city', 'cities of a region'), reinforcing the enum's meaning, and 'direct children' clarifies the hierarchy the parameters traverse. It adds no meaning for limit or cursor, leaving pagination undocumented on both sides.

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 and resource ('List the direct children of a place') and clarifies scope with concrete examples (neighbourhoods of a city, cities of a region). The parent/child framing naturally separates it from the venue-search and resolve siblings, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear use contexts: 'suggest areas to explore or to narrow a search', which tells an agent when this tool is appropriate relative to searching venues. It stops short of explicit exclusions or pointing at resolve_place as the prerequisite for place_id (that link only appears in the schema).

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.