Skip to main content
Glama
CiteContext MCP Server

CiteContext MCP Server

get_ai_search_cited_sources

Identify the external sources, reference URLs, and authority domains AI models cite for commercial queries, so you can target the content and domains that shape AI-generated answers.

Instructions

Identify which external sources, reference URLs, and authority domains AI models cite when answering commercial queries in your category.

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": {
      "query": "<query>"
    },
    "name": "get_ai_search_cited_sources"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesCommercial search query or prompt (e.g., 'best customer analytics tools for enterprise')
enginesNoEngines to inspect (e.g., ['claude', 'chatgpt', 'gemini'])
categoryNoOptional industry or product category

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing about execution: not whether live model queries are issued (cost/latency), how many engines are consulted by default, whether results are cached or time-scoped, or what a citation record looks like. For a tool that likely fans out to multiple LLM engines, that is a substantial gap.

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?

A single tightly packed sentence that front-loads the outcome (which sources get cited) rather than mechanics, with zero filler. It is efficient, though the tripled noun list ('external sources, reference URLs, and authority domains') is slightly redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, no annotations, and three parameters, the definition never explains what actually comes back — per-engine breakdowns, ranked URL lists, or domain authority groupings — nor which engines are queried if 'engines' is omitted. It is too thin for a tool with no structured return contract.

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 all three parameters (query, engines, category) are already documented, establishing a baseline of 3. The description adds only a light framing of the 'category' concept ('in your category') and nothing about engine selection behavior or defaults beyond what the schema states.

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 ('Identify') and a specific resource ('external sources, reference URLs, and authority domains AI models cite'), plus the scope ('commercial queries in your category'). This clearly separates it from something like get_ai_search_visibility, but it doesn't name or contrast any sibling explicitly, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'when answering commercial queries in your category' implies the use case (citation/source analysis for a commercial query set) but gives no explicit when-to-use, when-not-to-use, or which alternative to pick for visibility scoring versus citation sourcing. Guidance is inferable only.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.