Skip to main content
Glama

Nicolas Sitter Research

get_ai_hotel_landscape_manifest

Read-only

Read the manifest for the AI Hotel Landscape dataset: which AI platforms are tracked (ChatGPT, Gemini, Perplexity, Grok, Copilot, Google AI Mode) and whether each is still active, which of the 56 destinations are covered, which weekly snapshots exist, and the licence and refresh cadence. Call this FIRST before any other landscape tool, because it gives you the exact platform ids, city slugs and week dates the other tools expect. Use it whenever the user asks what data is available about how AI assistants recommend hotels.

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

Input Schema

NameRequiredDescriptionDefault
clientNoOptional: identify yourself, e.g. "my-agent/1.0". Not required and never used by the tool itself — recorded only so the public tracker at /projects/agent-tools can measure how many callers self-identify when nothing forces them to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds real value on top by describing the manifest's contents (active/inactive flags, snapshot availability, licence and refresh cadence) and the dependency relationship with other tools. It does not discuss response format or size, but for a read-only manifest that is a minor omission rather than a behavioral blind spot.

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?

Two sentences, front-loaded with the action and its contents, then the sequencing constraint. The platform enumeration (ChatGPT, Gemini, Perplexity, Grok, Copilot, Google AI Mode) is the only element that could be trimmed, though it usefully signals scope without a schema lookup.

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 no output schema, the description carries the return-value burden and does so by listing the manifest's four content areas plus licence and cadence. Combined with explicit first-call guidance and annotations covering safety, an agent has everything needed to invoke this correctly without further inspection.

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% and the only parameter (an optional client identifier) is fully documented in the schema as self-identification that the tool never uses. The description adds no parameter-level information, which is acceptable given the schema does the work, though it does not even note that all arguments are optional.

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 and resource ("Read the manifest for the AI Hotel Landscape dataset") and then enumerates exactly what it contains: tracked platforms, active status, the 56 destinations, weekly snapshots, licence and cadence. This distinguishes it immediately from data-querying siblings like get_ai_hotel_visibility or get_hotel_brand_leaderboard, whose names imply analysis rather than discovery.

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 an explicit ordering rule ("Call this FIRST before any other landscape tool") and explains why: it yields the platform ids, city slugs and week dates the other tools expect. It also states the triggering user intent ("whenever the user asks what data is available"). Both the when and the sequencing relative to alternatives are stated outright.

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