Skip to main content
Glama

List districts

list_districts
Read-onlyIdempotent

List the districts of one city that have active listings. Returns each district's slug, name and escort and venue counts. Most cities have none: an empty list means search the whole city. Use a district slug as district in search_listings.

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": {
      "country": "<country>",
      "city": "<city>"
    },
    "name": "list_districts"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesThe city whose districts to list: its `slug` from list_cities (e.g. "berlin").
countryYesThe city's `region` from list_cities: its country code, or its state code in a country the site splits by state (e.g. "US-CA").

Output Schema

NameRequiredDescriptionDefault
districtsYesDistricts with active listings; empty when the city has none.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / city / description
      Previous value: -"Required. City slug from list_cities."New value: +"The city whose districts to list: its `slug` from list_cities (e.g. \"berlin\")."
    • changedInput schema / properties / country / description
      Previous value: -"Required. The city's region from list_cities, or its ISO 3166-1 alpha-2 country code (e.g. \"DE\"), or a city's region code where the site splits a country by state (e.g. \"US-CA\"). Get valid values from list_countries / list_cities."New value: +"The city's `region` from list_cities: its country code, or its state code in a country the site splits by state (e.g. \"US-CA\")."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "districts": {
      +      "description": "Districts with active listings; empty when the city has none.",
      +      "items": {
      +        "properties": {
      +          "escortCount": {
      +            "description": "Active escort listings.",
      +            "type": "integer"
      +          },
      +          "name": {
      +            "description": "District name.",
      +            "type": "string"
      +          },
      +          "slug": {
      +            "description": "District slug, for `district`.",
      +            "type": "string"
      +          },
      +          "venueCount": {
      +            "description": "Active venue listings.",
      +            "type": "integer"
      +          }
      +        },
      +        "required": [
      +          "slug",
      +          "name"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "districts"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive behavior, so the safety profile is covered. The description adds genuinely non-obvious semantics: the list is filtered to districts with active listings, and emptiness is a common, meaningful result rather than an error. It slightly duplicates the returned-field list that the output schema already covers.

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?

Three short sentences, front-loaded with purpose and return shape, then the empty-result caveat and the handoff to search_listings. No filler or redundant restatement of the title.

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, full annotation coverage and fully documented parameters, the description only needs to supply the non-structured knowledge, which it does: the active-listings filter, the empty-result interpretation, and the follow-up call. Nothing needed to invoke it correctly is missing.

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 100%, and both parameters are documented in the schema with patterns and examples (city slug from list_cities, country as region/country code). The description adds no meaning about the parameters themselves, so the baseline of 3 applies.

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 ("List the districts of one city that have active listings") and states the scope constraint (only districts with active listings). It also lists the returned fields, so an agent can distinguish it from list_cities and search_listings without opening either schema.

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 downstream guidance: an empty list means search the whole city, and a returned slug should be passed as `district` to search_listings. This tells the agent both what to do with a hit and what to do with a miss, leaving little to inference.

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