Skip to main content
Glama

Paid public-data feeds (x402, 0.002 USD)

Sitemap facts for a site in one call: sitemap location (robots.txt aware), index or urlset, entry count, sample URLs, ne

sitemap
Read-onlyIdempotent

Sitemap facts for a site in one call: sitemap location (robots.txt aware), index or urlset, entry count, sample URLs, newest and oldest lastmod (url=https://example.com). Live request, public hosts only. Pay per call $0.002 USDC on Base via x402.

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

Input Schema

NameRequiredDescriptionDefault
urlNosite or origin
x_paymentNosigned x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent and non-destructive, so the bar is lower; the description still adds real context beyond them: the call makes a live network request, only public hosts are supported, and each call costs $0.002 USDC on Base via x402. It stops short of describing failure modes or rate limits.

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?

A single dense, front-loaded block that leads with the payoff ('in one call') and then lists returned facts, cost, and constraints. Nothing is redundant, though the packed comma-separated enumeration is slightly harder to scan than separate sentences.

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?

With no output schema, the description correctly carries the burden of explaining return values and does so field by field. The payment flow and public-host restriction are also disclosed; only error behavior and the required-payment path after the first call are left implicit.

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%, with both the url and x_payment parameters documented in the schema itself, including the first-call payment handshake. The description only adds the url example format (url=https://example.com), so the schema does the heavy lifting and the baseline of 3 applies.

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?

The description names the resource (sitemap) and enumerates exactly what facts are returned: sitemap location (robots.txt aware), index vs urlset, entry count, sample URLs, and newest/oldest lastmod. That is far more specific than a generic 'get sitemap', though it never explicitly distinguishes itself from siblings like page_meta or url_status.

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?

Constraints such as 'live request, public hosts only' and the pay-per-call model imply when this tool is appropriate, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative for cases like private or authenticated hosts.

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