Skip to main content
Glama

Direct Hotels

Check directory coverage

check_coverage
Read-onlyIdempotent

Whether the directory lists hotels in a place, and how many, without returning listings. Use when the user asks if a destination is covered, or before planning a trip around one. Deepest in the US and Western Europe, thin in China, the Gulf and much of Africa; an uncovered place comes back with covered places instead.

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": {
      "place": "<place>"
    },
    "name": "check_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
placeYesCity, region or country to check.
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.
countryNoCountry name or ISO code, if known.

Output Schema

NameRequiredDescriptionDefault
placeYes
hotelsYes
coveredYes
alternativesNo

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?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so safety is covered. The description goes beyond them by disclosing the coverage distribution (deep in the US and Western Europe, thin in China, the Gulf and much of Africa) and the important fallback behavior that an uncovered place returns covered places instead — a non-obvious return trait that materially changes how an agent should interpret results.

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. The core function leads, the usage condition follows, and the coverage caveat lands last where it is most likely to prevent a bad call.

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 present, return values need not be spelled out, and the description still supplies the one return nuance that matters (fallback to covered places). Annotations cover the safety profile and the schema covers all three parameters, leaving no meaningful gap for a read-only lookup tool.

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%, with 'place' documented as a city, region or country and 'client' explained as an optional, unused telemetry field. The description adds only the informal synonyms 'place'/'destination' and says nothing about the country parameter, so it neither compensates for nor improves on the schema.

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 opens with a specific verb-plus-resource statement: it reports whether the directory lists hotels in a place and how many, explicitly 'without returning listings.' That scope clause separates it cleanly from siblings like search_hotels and get_hotel, so an agent can pick it without opening a schema.

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?

It names two concrete trigger situations: when the user asks whether a destination is covered, and as a pre-check before planning a trip around one. It does not explicitly name an alternative tool to use instead when the user wants actual listings, though 'without returning listings' implies the boundary.

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