Skip to main content
Glama

Direct Hotels

About this directory

directory_info
Read-onlyIdempotent

What Direct Hotels is: a free, non-commission directory linking 425,000+ hotels to their own websites; its size, where coverage is thin, and what it does not hold (prices, availability, bookings). Use when the user asks what Direct Hotels is, how it makes money, or whether it can book.

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": "directory_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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 not open-world, so safety is covered. The description adds real domain context beyond that: the directory is free and non-commission, and it explicitly does NOT hold prices, availability, or bookings — a valuable negative disclosure that prevents wrong expectations about the answer.

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?

One dense, front-loaded sentence covering definition, scale, coverage, and exclusions, plus a second for usage. The semicolon-chained fragments ('its size, where coverage is thin') are slightly awkward but nothing is redundant.

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?

For a simple informational tool with no output schema and full annotation coverage, the description says what the tool answers, what data it adds, and what it will not return. Only minor gap is no hint about how the answer is presented (e.g., static summary vs. live counts).

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?

There is a single optional 'client' parameter with 100% schema description coverage, including its purpose and that it is not used by the tool. The description adds nothing about parameters, which is acceptable at this coverage level but yields no bonus.

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 subject (the Direct Hotels directory) and enumerates exactly what it covers: size (425,000+ hotels), thin-coverage areas, and what it does not hold (prices, availability, bookings). This is clearly the 'about the directory' tool, distinct from the lookup siblings like search_hotels or get_hotel.

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: 'Use when the user asks what Direct Hotels is, how it makes money, or whether it can book.' No when-not guidance or named alternatives, but the intent boundary against lookup tools is implied clearly enough by the content scope.

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