Skip to main content
Glama
CiteContext MCP Server

CiteContext MCP Server

search

Query the CiteContext public knowledge base for GEO playbook, AI citation research, llms.txt, and schema guidance to support ChatGPT Deep Research connectors.

Instructions

Search the CiteContext public knowledge base (GEO playbook, AI citation research, llms.txt and schema guides). Required search tool for ChatGPT Deep Research connectors.

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

Input Schema

NameRequiredDescriptionDefault
queryYesFree-text query (e.g. 'why is my brand not cited by ChatGPT')
max_resultsNoMaximum results to return (default: 8)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the burden, and it does usefully disclose that the target is a public (hence unauthenticated, read-only) documentation corpus, which shapes expectations about results. However, it says nothing about ranking, result shape, pagination, or rate limits, leaving meaningful behavioral gaps for a search endpoint.

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 front-loaded sentences with no filler; the corpus scope leads. The second sentence is slightly meta about the connector integration but does convey real context about when the tool is exercised, so it earns its place.

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

Completeness3/5

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

For a simple two-parameter read tool this covers what is searchable and why it exists, but with no output schema it should say something about what a result contains (title, URL, snippet) so the agent knows what it can cite downstream. That gap keeps it at minimum-viable completeness.

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 both parameters are documented in the schema, including a concrete query example and the max_results default. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

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 ('Search the CiteContext public knowledge base') and enumerates the corpus contents (GEO playbook, AI citation research, llms.txt and schema guides), which makes it distinguishable from data-returning siblings like get_ai_search_visibility or geo_audit_domain. It stops short of explicitly naming an alternative, so it falls just under the top mark.

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 note that this is the 'required search tool for ChatGPT Deep Research connectors' implies the context in which it is expected, but there is no explicit when-to-use/when-not guidance and no routing to sibling tools. An agent must infer that this is for documentation lookup rather than site data retrieval.

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