Skip to main content
Glama

List places

list_places
Read-only

Use it when the person asks where this site's yachts leave from, or a place name they said is shared by two places. It answers how many regions, countries, areas, towns and bases there are, then one page of those places, each with its id and how many yachts are there now, read from the live inventory. Pass text with the name the person said to find that place on the first page, and level to list only one kind of place. When placesPage.cursor is not null, pass it as cursor for the next page. Pass an id to search_yachts as placeId to search exactly that place, for example when a name the person said is shared by two places. Arguments: text, level, cursor, limit. Any other name is refused.

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

Input Schema

NameRequiredDescriptionDefault
textNoPart of a place's name, in the person's words: only places whose name holds every word (any case).
levelNoOnly this kind of place.
limitNoRows per page: at most 50 without sign-in, 20 for a signed-in person.
cursorNoThe cursor a previous answer returned, for its next page.

Output Schema

NameRequiredDescriptionDefault
countsYesHow many places of each level there are in all (region, country, area, town, base).
placesYesEvery region, country, area, town and base, as the source links them.
freshnessYesThe copy of the source this answer reads.
placesPageYesThis page: total places (of the asked level) and the cursor for the next page, null on the last.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Rows per page: 50 when not given; at most 50 when browsing, 20 once the person is signed in."New value: +"Rows per page: at most 50 without sign-in, 20 for a signed-in person."
  2. Changed7 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
      +  "description": "The cursor a previous answer returned, for its next page.",
      +  "type": "string"
      +}
    • addedInput schema / properties / level
      Added value: +{
      +  "description": "Only this kind of place.",
      +  "enum": [
      +    "region",
      +    "country",
      +    "area",
      +    "town",
      +    "base"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Rows per page: 50 when not given; at most 50 when browsing, 20 once the person is signed in.",
      +  "type": "number"
      +}
    • addedInput schema / properties / text
      Added value: +{
      +  "description": "Part of a place's name, in the person's words: only places whose name holds every word (any case).",
      +  "type": "string"
      +}
    • addedOutput schema / properties / counts
      Added value: +{
      +  "description": "How many places of each level there are in all (region, country, area, town, base).",
      +  "type": "object"
      +}
    • addedOutput schema / properties / placesPage
      Added value: +{
      +  "description": "This page: total places (of the asked level) and the cursor for the next page, null on the last.",
      +  "properties": {
      +    "cursor": {
      +      "description": "Pass as cursor for the next page; null on the last.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "total": {
      +      "description": "Places in all, of the asked level.",
      +      "type": "number"
      +    }
      +  },
      +  "type": "object"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "places",
      -  "freshness"
      -]New value: +[
      +  "places",
      +  "counts",
      +  "placesPage",
      +  "freshness"
      +]
  3. Changed1 schema field changed
    • addedOutput schema / properties / places / items / properties / placeId
      Added value: +{
      +  "description": "Its typed id, \"<level>:<id>\": search takes it as placeId and it names this place only.",
      +  "type": "string"
      +}
  4. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare a read-only, closed-world, non-destructive operation, and the description adds that results come from live inventory and that the answer is paginated with a cursor. It also states that unknown argument names are refused, which is a real behavioral trait not visible in annotations, though it does not discuss result ordering or empty-result behavior.

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 triggering situation and the returned shape, and every clause carries information. Some sentences run long and the argument list at the end is close to restating the schema, but nothing is truly redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 document return values, yet it still flags placesPage.cursor for paging and the id-to-placeId handoff. For a four-optional-parameter list tool this covers everything an agent needs before calling.

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?

Schema coverage is 100%, so baseline is 3, but the description adds genuine meaning: text matches the name 'in the person's words' and returns that place on the first page, level restricts to one kind of place, and cursor chains pages. It also links the returned place id to search_yachts's placeId, which the schema cannot express.

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?

The description names a specific verb and resource and scopes it: it reports how many regions, countries, areas, towns and bases exist, then one page of those places with id and live yacht counts. It also distinguishes itself from search_yachts by routing to that sibling when an exact place is known.

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

Usage Guidelines5/5

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

It gives concrete trigger conditions ('when the person asks where this site's yachts leave from, or a place name shared by two places'), an explicit alternative (pass the id to search_yachts as placeId), and the pagination rule (when placesPage.cursor is not null, pass it as cursor).

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