Place to Be

List covered cities

list_cities

Read-only

List the cities that currently have a live events board, with how many upcoming events each holds, biggest first. Filter by part of a name or by country. Use it to check coverage or to find the exact city name before calling search_events.

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

Input Schema

Name	Required	Description
`limit`	No
`query`	No	Part of a city name, e.g. "san" or "York".
`country`	No	English country name or ISO 3166-1 alpha-2 code.

Output Schema

Name	Required	Description
`count`	Yes
`cities`	Yes
`total_cities`	Yes	Cities with a live board, before filtering.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 30, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds the useful behavioral detail of result ordering (largest event count first) and that only cities with a live board are returned. It does not mention the default/max result count behavior, but that is minor against the annotation coverage.

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 sentences, zero filler, with the what/ordering stated first and the routing/usage guidance second. Every clause earns its place.

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?

An output schema exists, so return-value structure need not be explained. Given a read-only, annotation-covered list tool with three simple params, the description supplies everything an agent needs to select and call it correctly.

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 67%, and the description reinforces the two documented filters (partial name match, country) but adds no new syntax or format detail beyond the schema. The 'limit' parameter is undocumented in both the description and the schema, so the description does not compensate for the coverage gap.

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 states a specific verb and resource ('List the cities that currently have a live events board') plus scope and ordering ('biggest first'), so the agent knows exactly what comes back. It also differentiates itself from the sibling search_events by framing itself as a coverage/name-resolution lookup rather than an event search.

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 explicit when-to-use guidance ('Use it to check coverage or to find the exact city name before calling search_events'), naming the sibling it feeds into. The filtering options (part of a name, country) are also tied to concrete intent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Place to Be tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?