Skip to main content
Glama

Direct Hotels

Find covered cities

find_city
Read-onlyIdempotent

Covered cities matching a few letters of a name, with hotel counts. Use when the user's place is partial, misspelled or ambiguous, before search_hotels.

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": {
      "query": "<query>"
    },
    "name": "find_city"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesPartial city name, e.g. "marra", "tok".
clientNoOptional: your product or agent name, e.g. "Claude". Not used by the tool; recorded only for the public count of which assistants use the directory.

Output Schema

NameRequiredDescriptionDefault
matchesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive behavior, so the bar is lower. The description adds real value beyond them: fuzzy/partial matching semantics and the fact that results are limited to the covered-city directory with hotel counts attached.

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?

A single sentence carries purpose, output attribute, trigger conditions and sequencing relative to a sibling, with the identifying information front-loaded and 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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile; the description supplies matching mode, scope and follow-up tool. Minor gap: nothing is said about behavior when no city matches.

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 coverage is 100%, with the query parameter already documented as a partial name with examples, so the schema does the heavy lifting. The description reinforces partial-match intent but adds no new detail about the query format or about the optional client parameter.

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 action (find/matching), a specific resource (covered cities), the matching mode (a few letters of a name) and an output attribute (hotel counts). An agent can immediately tell this is a fuzzy city typeahead, distinct from search_hotels or check_coverage.

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?

Gives explicit trigger conditions (place is partial, misspelled or ambiguous) and an ordering instruction (before search_hotels), which routes the agent correctly. It stops short of stating when not to use it, e.g. when an exact city identifier is already known, so it falls just short of full coverage.

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