Skip to main content
Glama
geo-seo-readiness-lite

geo-seo-readiness-lite

quick_readiness_report

Read-only

Runs AI crawler, llms.txt, JSON-LD/canonical, and sitemap checks for a URL, then returns a prioritized fix list so you can improve AI search readiness.

Instructions

Run all checks (AI crawler access, llms.txt, JSON-LD/canonical, sitemap) for a URL and return a prioritized fix list.

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic page or site URL, e.g. https://example.com/pricing

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true), so the bar is lower, and the description still adds real value by disclosing exactly which four check families run and that the result is a prioritized fix list rather than raw per-check output. It stops short of mentioning latency, network cost, or what happens on partial failures, which keeps it from a 5.

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?

One sentence, front-loaded with the action, dense in content and free of filler. Every clause carries information the agent needs (which checks, what input, what output).

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 read-only, single-parameter aggregate tool, the description covers action scope and return shape (prioritized fix list) sufficiently despite the absence of an output schema. A minor gap remains around whether it accepts a site root vs a single page and how the prioritization is expressed, but the essentials for correct invocation are present.

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% and the single 'url' parameter is fully documented in the schema (public page or site URL with an example). The description's 'for a URL' adds no meaning beyond that; baseline 3 for a fully-covered schema is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb ('Run all checks') plus enumerated resources (AI crawler access, llms.txt, JSON-LD/canonical, sitemap) and a stated output ('prioritized fix list'). The phrase 'all checks' makes it distinguishable from the single-purpose siblings (check_ai_crawler_access, check_llms_txt, check_sitemap, extract_structured_data) without needing to name them.

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 rather than stated: an agent can infer this is the comprehensive/audit option while siblings are the granular ones. There is no explicit when-to-use vs when-to-use-a-single-check guidance, no prerequisites, and no exclusions, so the routing decision is left partly to inference.

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