Skip to main content
Glama

BRAINIAC Technical SEO Audits

Validate a sitemap or sitemap index

seo-technical_xml-sitemap-validate
Read-onlyIdempotent

Check sitemap URL counts, absolute locs, lastmod/changefreq/priority and size limits against the sitemaps.org protocol. Price $0.03 USDC. POST /api/v1/seo-technical/xml-sitemap-validate. An unpaid call returns the x402 payment terms and does not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "seo-technical_xml-sitemap-validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
xmlNoxml, string, length 0 to 55000000. Optional.
gzipBase64NogzipBase64, value. Optional.
sitemapUrlNositemapUrl, string, uri. Optional.

Output Schema

NameRequiredDescriptionDefault
typeNotype. String.
bytesNobytes. Number.
errorsNoerrors. Array.
sourcesNosources. Array.
urlCountNourlCount. Number.
warningsNowarnings. Array.
duplicatesNoduplicates. Number.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), but the description adds genuinely new behavior: cost of $0.03 USDC, the POST endpoint, and crucially that an unpaid call returns x402 payment terms without executing. That payment-gating behavior is not derivable from structured fields and prevents wasted calls.

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?

Three compact sentences, front-loaded with what gets validated, then commercial terms, then payment failure behavior. The literal route string 'POST /api/v1/seo-technical/xml-sitemap-validate' is marginally redundant with the tool name, but the rest is tight and earns its space.

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?

An output schema exists, so return values need not be explained, and annotations carry the safety profile. Given the low complexity, what remains missing is modest: guidance on mutually exclusive input modes and minimum input requirement, but an agent has enough to invoke it correctly.

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 coverage is 100%, so all three parameters (xml, gzipBase64, sitemapUrl) are documented in the schema itself, establishing a baseline of 3. The description does not clarify that these are alternative input modes or that at least one presumably must be supplied despite zero required parameters, which would have added meaning beyond the schema.

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?

States a specific verb ('Check') plus the exact resource and checks performed: URL counts, absolute locs, lastmod/changefreq/priority, and size limits against the sitemaps.org protocol. This distinguishes it clearly from sibling validators like hreflang-validate and schema-org-validate, which validate different artifacts.

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 infers it should call this when it has sitemap XML, gzip content, or a sitemap URL to check. There is no explicit when-to-use, when-not-to-use, or routing to a sibling tool, and no guidance on which of the three alternative input modes to pick.

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