Skip to main content
Glama

Direct Hotels

Suggest a missing hotel

suggest_hotel
Idempotent

Sends Direct Hotels a hotel it does not list, for review. Use when the user names a hotel that search_hotels and get_hotel did not find and wants it added. We check the hotel's own website before listing it (usually within minutes, otherwise after a manual review), so a suggestion is not yet a listing. The website, when known, is what we verify against. Stores the hotel's details only, nothing about the user.

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": {
      "hotel_name": "<hotel_name>",
      "city": "<city>"
    },
    "name": "suggest_hotel"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCity or town, e.g. "Rethymno".
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.
websiteNoThe hotel's own website, not a booking platform.
hotel_nameYesThe hotel's name, e.g. "Hotel Elida".

Output Schema

NameRequiredDescriptionDefault
statusYes
messageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false; the description adds value beyond them by disclosing the review lifecycle ('usually within minutes, otherwise after a manual review'), the verification source (the hotel's own website), and the data-storage scope ('details only, nothing about the user'). Those are exactly the facts an agent needs before submitting.

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?

Four short sentences, front-loaded with the action and the when-to-use condition, then the review timing, then the privacy note. No sentence restates the title or repeats the schema without adding a reason.

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?

An output schema exists, so return shape need not be described. Between the annotations and the description, an agent knows what the tool does, when to call it, how long review takes, and what data is retained — nothing material is missing for a five-parameter submission 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%, so the schema already explains every parameter, including that website must be the hotel's own site rather than a booking platform. The description reinforces why the website matters — it is what verification runs against — but adds no format or constraint detail beyond that. Baseline 3 is appropriate.

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 concrete verb and resource: 'Sends Direct Hotels a hotel it does not list, for review.' It also clarifies the outcome ('a suggestion is not yet a listing'), which separates it from any listing-creation tool, and names the two sibling tools whose failure precedes it.

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?

Gives an explicit trigger — 'Use when the user names a hotel that search_hotels and get_hotel did not find and wants it added' — naming both the prerequisite tools and the user intent. It also sets the expectation that the suggestion is provisional, which is the key decision factor for an agent.

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