Skip to main content
Glama

List djbnb cities

list_cities
Read-onlyIdempotent

Lists the US cities djbnb covers, each with its slug and the links to its tonight and this weekend pages. Use the slug with whos_playing.

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.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so safety is covered. The description adds scope the annotations do not: the coverage is US cities only, and each entry carries a slug plus links to tonight and weekend pages — useful behavioral detail about what the result contains, especially since no output schema exists.

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, both load-bearing: the first defines the output, the second tells the agent what to do with it. The result-defining content is front-loaded and there is no filler.

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 no output schema, the description usefully sketches the return values (slug, tonight page, weekend page links), which is the key information an agent needs. It could still be richer — e.g., whether the list is exhaustive or paginated, and whether ordering is stable — but for a simple zero-param enumeration it is close to sufficient.

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 no parameters (baseline 4) and the schema confirms an empty, closed object. The description correctly spends no words on parameters and instead explains the shape of the returned entries.

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 ('Lists') and resource ('US cities djbnb covers'), and further specifies the payload contents (slug plus tonight/weekend page links). It reads clearly as a discovery/enumeration tool and is distinguishable from the sibling whos_playing, which it names.

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?

Explicitly routes the agent forward: 'Use the slug with whos_playing,' which tells the agent this is a prerequisite lookup for the sibling tool. It does not state any when-not-to-use conditions, but for a zero-parameter enumeration tool there is little ambiguity to resolve, so the gap is minor.

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