Skip to main content
Glama

audit_geo

Read-onlyIdempotent

Full GEO (AI-search visibility) readiness audit of a brand/storefront URL. Fetches the site server-side and runs 20 weighted checks across schema.org depth (Organization, Product, Review, FAQPage, aggregateRating), business identity (sameAs, NAP consistency, contact), AI-crawler policy (robots.txt treatment of GPTBot/ClaudeBot/PerplexityBot/CCBot, llms.txt), content extractability (clean text, headings, JS walls, meta description), freshness (sitemap, lastmod, content dates), and authority (about page, credentials, canonical/HTTPS). Returns machine-readable JSON: 0-100 score, A-F grade, per-check pass/partial/fail/unknown with evidence, and the top 3 prioritized fixes. No LLM is queried per call — deterministic checks only. Cost: $1.50 USDC on Base per call, paid via x402 — the caller's agent pays from its owner's approved wallet; no API key needed. Use this to audit a client's site for AI-search visibility, or to generate the audit behind a GEO report for a brand owner.

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_geo"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesBrand/storefront URL to audit, e.g. https://example-brand.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes well beyond them: deterministic checks with no per-call LLM, server-side fetch, the exact $1.50 USDC-on-Base x402 payment flow with no API key, and what the JSON payload contains. Cost and payment mechanics are behavior an agent genuinely needs and cannot get from annotations or 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?

Front-loads purpose, then the check categories, then output shape, then cost — a sensible ordering with no filler sentences. The parenthetical enumerations are long but each item carries selection-relevant signal; only minor tightening is possible.

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

Completeness5/5

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

There is no output schema, and the description compensates fully by describing the return payload (0-100 score, A-F grade, per-check pass/partial/fail/unknown with evidence, top 3 fixes). For a single-parameter audit tool, nothing needed to invoke it or interpret results is missing.

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?

One parameter with 100% schema description coverage, so the baseline is 3. The description reinforces that the URL must be a brand/storefront site fetched server-side (implying a live, publicly reachable URL), but adds no format or validation detail beyond the schema example.

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?

Specific verb and resource: a 'full GEO readiness audit of a brand/storefront URL', with the 20 check categories enumerated so the agent knows the scope precisely. It signals differentiation from a lighter sibling by calling itself 'Full' and naming the check families, but it never names audit_geo_lite or states the boundary between them, so an agent must infer which to call.

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

Usage Guidelines4/5

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

Gives clear usage context: 'audit a client's site for AI-search visibility' or 'generate the audit behind a GEO report for a brand owner'. No exclusions or explicit alternative are named, so when a lighter/cheaper audit_geo_lite is the right choice is left to inference, especially relevant given the $1.50 per-call cost disclosed later.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources