Skip to main content
Glama

Site map

site_map

Every URL a website publishes in its own sitemaps (robots.txt, nested indexes, gzip), each with its lastmod, up to 5,000; a site without a sitemap is not charged. $0.003 per call over x402.

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

Input Schema

NameRequiredDescriptionDefault
urlYesany page of the site
paymentNoa signed x402 payment (the same base64 payload you would put in the PAYMENT-SIGNATURE header). Pass it here and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the transparency burden and discloses key behavior: sitemap sources, lastmod inclusion, a 5,000-URL cap, the no-sitemap no-charge rule, and per-call pricing over x402. It still leaves truncation behavior, error handling, and output shape unspecified.

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?

The description is a single, front-loaded sentence that packs the returned resource, sitemap sources, cap, and billing terms without filler. Every clause carries useful information.

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 tool with no output schema, the description covers what is returned, where it comes from, the 5,000-item limit, and the no-sitemap billing exception. It is nearly complete, though it could state truncation or failure behavior more explicitly.

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 the schema already defines both the url and payment parameters. The description adds billing context but does not deepen parameter semantics beyond what the schema provides.

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 states a specific resource and scope: URLs published in a website's own sitemaps, including robots.txt, nested indexes, and gzip. It is clear what the tool returns, but it does not explicitly name sibling tools such as site_extract or page_markdown to sharpen differentiation.

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 sitemap focus and the no-sitemap billing note, so an agent can infer this is for sitemap discovery rather than page content extraction. However, there is no explicit when-to-use versus alternatives guidance or stated exclusions.

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