Skip to main content
Glama

Nicolas Sitter Research

get_chain_vs_independent_mix

Read-only

Get the share of chain hotels versus independents versus vacation rentals in what each AI platform recommends, for one week. Use this when the user asks whether AI assistants favour big chains over independent hotels, whether an independent property can compete in AI answers, or how the platforms differ in the kind of property they surface.

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

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. Omit for all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/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 a real behavioural fact beyond that: results are aggregated per AI platform and bounded to a single week snapshot. It says nothing about response shape, sample sizes, or whether platforms with sparse data are omitted.

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: the first front-loads what the metric is, the second enumerates the selecting questions. The second sentence is long but each clause corresponds to a distinct trigger, so little is wasted. Slightly tighter phrasing of the category list would earn a 5.

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 read-only, zero-required-parameter aggregate query with no output schema, the definition covers purpose, scope, and invocation triggers adequately. The remaining gap is knowing what a result row looks like, but with no output schema declared that burden is minimal.

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 week and platform parameters already document their own formats and omit-for-default behavior. The description adds only the notion that results are per-platform and per-week, which is a conceptual framing rather than parameter-level guidance. Baseline 3 is appropriate because the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: the share of chain hotels vs independents vs vacation rentals in AI platform recommendations, scoped to one week. It also names the three categories being compared, which the tool name alone does not reveal. It does not explicitly distinguish itself from the closest sibling, get_hotel_brand_leaderboard, leaving overlap for the agent to resolve.

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 concrete user-question triggers: whether AI assistants favour chains, whether independents can compete, and how platforms differ in surfaced property types. That is clear usage context rather than a vague 'use for analysis'. It stops short of stating when NOT to use it or which sibling to pick for brand-level or hotel-level questions.

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