Skip to main content
Glama
CiteContext MCP Server

CiteContext MCP Server

audit_page_geo

Run a page-level GEO audit on a single URL to check factual density, heading chunking, Schema JSON-LD, and token efficiency, revealing what limits AI citability.

Instructions

Run a deep page-level Generative Engine Optimization (GEO) audit on a single URL. Analyzes Princeton KDD factual density, H1/H2 chunking, Schema JSON-LD, and context window token efficiency.

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": {
      "url": "<url>"
    },
    "name": "audit_page_geo"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesFull page URL to audit (e.g. 'https://example.com/pricing' or 'https://example.com/docs')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It names the analysis dimensions but says nothing about whether the page is fetched live, whether the call is read-only, expected duration or rate limits, whether results are cached, or what the response looks like — meaningful gaps for an analysis job with no output schema.

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, front-loaded with the action and scope, then a compact list of what gets measured. No filler, though the jargon phrases ('Princeton KDD factual density', 'context window token efficiency') are opaque without expansion and slightly reduce immediate comprehension.

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 one-parameter tool this covers purpose and scope adequately, but with no annotations and no output schema the description should say more about what the audit returns and how long/how costly the deep analysis is. An agent knows what to call it on but not what to expect back.

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% for the single required 'url' parameter, and the schema already explains the full-URL format with examples. The description only reinforces scope ('single URL', 'page-level') without adding format, validation, or edge-case detail beyond the schema, 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 ('Run a deep page-level GEO audit on a single URL') and enumerates what is analyzed (factual density, H1/H2 chunking, Schema JSON-LD, token efficiency). The 'page-level'/'single URL' framing implicitly separates it from the domain-level sibling geo_audit_domain, but it never names that alternative explicitly, so the differentiation is inferred rather than stated.

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: by describing itself as a single-URL page audit, an agent can guess this is the per-page counterpart to a domain audit. There is no explicit when-to-use, when-not, prerequisite (e.g., whether the page must be publicly reachable), or named alternative, leaving routing decisions to inference.

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