Skip to main content
Glama

Nicolas Sitter Research

get_hotel_brand_leaderboard

Read-only

Get the chain-brand leaderboard for one AI platform in one week: which hotel groups (Marriott, Accor, Hilton, IHG and the rest) get mentioned most, and across how many distinct properties. Use this when the user asks which hotel chains or brands dominate AI recommendations, how a specific group performs against its competitors in AI answers, or whether big brands beat independents. For individual properties use get_ai_hotel_visibility instead.

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_hotel_brand_leaderboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
weekNoSnapshot week as YYYY-MM-DD. Omit for the most recent.
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.
platformNoPlatform id from the manifest.

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 declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds useful context beyond that: the leaderboard ranks by mention frequency and distinct property count, which tells the agent what the output measures. It does not discuss pagination or scope limits, but for a read-only lookup this is solid.

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?

Front-loads the core purpose, then usage triggers, then the alternative. Efficient overall, though the first sentence is long enough that the alternative redirect sits far from the resource definition.

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?

For a read-only leaderboard tool with no output schema, the description conveys what is measured (mentions, distinct properties), the unit of aggregation (platform × week), and the correct routing away from property-level queries. An agent has everything it needs to call this correctly.

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%, so all three parameters are already documented. The description implies a week and platform scope but adds no format or syntax details beyond the schema; the baseline of 3 applies when the schema does the heavy lifting.

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 verb and resource ('chain-brand leaderboard'), scopes it to one platform and one week, and names the sibling it is not ('get_ai_hotel_visibility' for individual properties). The agent can distinguish it from siblings without opening the schema.

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 three explicit trigger questions ('which hotel chains dominate AI recommendations', 'how a specific group performs against competitors', 'whether big brands beat independents') and routes the individual-property case to a named alternative. Nothing is left to inference.

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