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

geo-seo-readiness-lite

check_sitemap

Read-only

Locates a website's XML sitemap via robots.txt or /sitemap.xml, then counts its URLs and handles gzip files up to 4 MiB.

Instructions

Find the XML sitemap (robots.txt Sitemap: lines or /sitemap.xml) and count its URLs. Reads up to 4 MiB; supports gzip.

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

Input Schema

NameRequiredDescriptionDefault
urlYesSite URL
sitemap_urlNoOptional explicit sitemap URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description's added value is operational: it discloses the 4 MiB read cap and gzip support, which materially affect whether the call succeeds on large sitemaps. It does not say what happens on a missing sitemap or a truncated read, but the network/limit caveats are the useful ones here.

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 short sentences, front-loaded with the action and result, with the size/gzip caveats trailing as a qualifier. No filler and nothing repeated from the name or annotations.

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 two-parameter read-only fetch with full schema coverage and no output schema, the description covers source discovery, override behavior implicitly, and size/encoding limits. The only real gap is the failure/no-sitemap case, which is minor for this complexity.

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%, so both `url` and `sitemap_url` are already documented, and the baseline is 3. The description alludes to fallback discovery paths but does not explain how `sitemap_url` overrides them, so it adds no semantics beyond 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?

States a specific verb+resource ('Find the XML sitemap ... and count its URLs') and even names the discovery mechanisms (robots.txt Sitemap: lines or /sitemap.xml). It does not explicitly contrast with siblings like check_llms_txt, but the sitemap scope is unambiguous.

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: an agent can infer this is the sitemap-discovery variant of the site-check family, and the parenthetical clarifies which sources are consulted. There is no explicit 'use this when X, use sibling Y when Z' guidance or prerequisite note.

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