Skip to main content
Glama

Nicolas Sitter Research

get_ai_citation_sources

Read-only

Get what an AI platform cites when it answers hotel questions — the mix of source categories (OTAs, review sites, the hotels' own sites, editorial, and so on) and the leading domains inside each category. Use this when the user asks where ChatGPT or Perplexity gets its hotel information, which sites influence AI recommendations, whether a domain is cited by AI assistants, or how to get cited. This is the question behind most AEO and GEO work.

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

Input Schema

NameRequiredDescriptionDefault
cityNoCity slug or name. Omit for all destinations.
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. Naming one also returns top domains per category.

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 value by describing the shape of the answer (category mix plus top domains per category), which matters given there is no output schema. However, it says nothing about snapshot semantics, data freshness, or coverage limits, which are real behavioral traits for a citation dataset.

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?

Three sentences: purpose first, then concrete usage triggers, then a short framing line. It is front-loaded and free of redundancy, though the closing 'This is the question behind most AEO and GEO work' is positioning language that adds little operational value.

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, four-optional-parameter retrieval tool with no output schema, the description does the essential work: it says what comes back and when to call it. The remaining gap is temporal — nothing in the description tells an agent that results are weekly snapshots, so freshness behavior is only discoverable from the schema.

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% and all four parameters are optional and already documented, so the baseline applies. The description adds no parameter-level meaning — notably it does not explain the relationship between platform selection and the per-category domain breakdown, which the schema only hints at.

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?

The description gives a specific verb and resource ('Get what an AI platform cites when it answers hotel questions') and enumerates the returned content precisely: source-category mix (OTAs, review sites, hotel sites, editorial) plus leading domains per category. It is clear without opening the schema, but it never names or contrasts a sibling such as get_ai_hotel_visibility, so the differentiation is left to inference.

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?

It supplies four concrete trigger questions (where ChatGPT/Perplexity gets hotel info, which sites influence AI recommendations, whether a domain is cited, how to get cited), which is strong positive routing guidance. It stops short of exclusions — nothing says when to prefer get_ai_hotel_visibility or the manifest instead — so it does not reach a 5.

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