Skip to main content
Glama
CiteContext MCP Server

CiteContext MCP Server

geo_audit_domain

Audit a website domain's Generative Engine Optimization readiness across eight categories by checking AI bot directives, llms.txt, JSON-LD schema, and citability factors.

Instructions

Run an 8-category Generative Engine Optimization (GEO) audit on any website domain. Evaluates robots.txt AI bot directives, llms.txt availability, JSON-LD Schema veracity, and Princeton KDD citability factors.

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": {
      "domain": "<domain>"
    },
    "name": "geo_audit_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
nicheNoOptional category/niche (e.g. 'B2B SaaS', 'E-commerce')
domainYesDomain name or website URL to audit (e.g., 'citecontext.com' or 'https://acme.org')
brand_nameNoOptional brand or product name (defaults to domain name)

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?

No annotations are provided, so the description carries the full burden. It usefully discloses the audit dimensions (robots.txt AI bot directives, llms.txt, JSON-LD schema, citability factors), but says nothing about whether it mutates anything, how long a multi-category crawl takes, network/permission requirements, or failure behavior.

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 core action and then the concrete checks performed; every clause carries information. Mild jargon ('Princeton KDD citability factors') is the only element that could slow an agent's 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?

With no annotations and no output schema, the description should say more about what the audit returns and roughly what it costs to run. It conveys the scope of the analysis but leaves the result shape and operational characteristics to inference.

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%, with domain, niche, and brand_name all documented with examples, so the baseline is 3. The description adds no additional meaning about how niche or brand_name influence the audit categories, so it does not exceed the schema.

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 and resource ('Run an 8-category Generative Engine Optimization (GEO) audit on any website domain') and enumerates what the audit checks. The domain-level scope implicitly separates it from the page-level sibling audit_page_geo, but no sibling is named explicitly.

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 the scope word 'domain' — there is no explicit statement of when to choose this over audit_page_geo or check_ai_bot_access, and no prerequisites or exclusions. An agent can infer a whole-site audit from the description, but must reason about alternatives itself.

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