Skip to main content
Glama

MagicGEO — AI Search & Commerce Agent Seller

GEO audit of a URL

geo_audit
Read-onlyIdempotent

Audit how readable and citable a public URL is for AI engines (ChatGPT, Perplexity, Google AI Overviews): Schema.org JSON-LD types, llms.txt, meta/OG tags, alt text, AI crawler access. Returns a 0-100 GEO score and per-check breakdown.

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic URL to audit, e.g. https://example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, and open-world, so the safety and side-effect profile is covered. The description adds real value by listing the checks performed and stating the return shape (0-100 score plus per-check breakdown), but it says nothing about whether a live fetch occurs, timeouts, rate limits, or failure behavior for unreachable pages.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences with no filler: the first is front-loaded with the purpose and scope, the second delivers the return contract. Every clause (engine list, check list, score range) carries information an agent would otherwise have to guess.

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 single-argument read-only tool this covers purpose, scope, what is examined, and what comes back, which is enough to call it correctly. Since no output schema exists, the description could say slightly more about the granularity of the per-check breakdown, but nothing essential is missing.

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?

With one parameter at 100% schema coverage the schema already documents the argument and gives an example, so the baseline is 3. The description earns the extra point by qualifying the URL as 'public', which is a meaningful constraint the schema does not express.

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 ('Audit ... a public URL') and enumerates exactly what is inspected (JSON-LD types, llms.txt, meta/OG tags, alt text, crawler access), so the scope is unambiguous. It stops short of naming any sibling, so differentiation from geo_benchmark or geo_citation is left to inference from the 'single public URL' scoping.

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 implied by the framing ('for AI engines') and by the 'public URL' constraint, which tells an agent localhost or auth-gated targets won't work. There is no explicit when-to-use vs. when-to-use-an-alternative statement and no mention of prerequisites or follow-up tools.

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