Skip to main content
Glama

List Cities

list_cities
Read-only

List the cities Moments covers, with the slug to use in search_events and the city page URL. Data is public Moments event listings for Norwegian and other cities. Event texts come from third-party organizers.

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

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

readOnlyHint=true already establishes the safety profile, and the description adds meaningful context beyond it: the data is public Moments event listings, and event texts originate from third-party organizers, which warns the agent about provenance and accuracy. It omits details like list size, caching, or update cadence, so it is not exhaustive.

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?

Two tight sentences, front-loaded with the core action and return shape, followed by a provenance caveat. The third-party organizer note is slightly tangential to a city list but still earns its place as a data-quality warning.

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?

There is no output schema, so the description carries the burden of describing return contents, and it does so (slug plus city page URL) while also scoping the dataset to Norwegian and other cities. For a zero-parameter, read-only listing tool this is nearly sufficient; only list size or ordering behavior is unstated.

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 of 4 applies; no parameter semantics are required or missing.

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?

States a specific verb and resource ("List the cities Moments covers") and immediately names what each entry contains: the slug and the city page URL. The mention that the slug is what you pass to search_events distinguishes it from the sibling event tools without ambiguity.

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?

Implies a clear workflow: call this to obtain a slug before using search_events, which is genuinely useful routing guidance. It does not state exclusions or when this tool is unnecessary (e.g., if a slug is already known), so it falls short of explicit when-not guidance.

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