Skip to main content
Glama
CiteContext MCP Server

CiteContext MCP Server

fetch

Retrieve the full readable text of a CiteContext knowledge-base page by ID or URL for ChatGPT Deep Research connectors.

Instructions

Fetch the full readable text of a CiteContext knowledge-base page by id/URL. Required fetch 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": {
      "id": "<id>"
    },
    "name": "fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPage id or URL as returned by search (e.g. 'https://citecontext.com/blog/geo-vs-seo')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the full behavioral burden. It usefully discloses that the returned value is 'full readable text' (cleaned, not raw HTML), but it omits error behavior for invalid ids, truncation or size limits for long pages, and whether any authentication is required.

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?

The description is two short sentences that lead with the core action, which is efficient. The second sentence is more about the connector context than about how to call the tool, so it does not fully earn its place, but it is not harmful.

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 simple one-parameter read tool with 100% schema coverage and no output schema, the definition covers the essential purpose and the shape of the return value. The only missing pieces are edge-case behavior (not-found, truncated pages), which are minor for a tool this simple.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only one parameter is provided, and the schema covers it fully: it accepts either an id or a URL, and the schema gives an example. The description adds only a small clarification by restating that the value can be an id or a URL, so this dimension has little room to exceed the schema baseline of 3–4.

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 names a specific verb (Fetch), resource (CiteContext knowledge-base page), and scope (full readable text, by id/URL). It is clearly distinct from search, since this returns one page's text rather than result sets. It falls short of a 5 only because it doesn't explicitly name the sibling tool it pairs with.

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?

Usage is only implied: the id is described as 'as returned by search', which hints that this tool is used after search, and the second sentence frames it as required for ChatGPT Deep Research connectors. There is no explicit instruction about when to use this tool versus search or when not to call it (e.g., pages already in context).

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