Skip to main content
Glama

BRAINIAC Web & Page Intelligence

Index sitemap content

web-intelligence_sitemap-content-index
Read-onlyIdempotent

Fetch one public sitemap or sitemap index and return the listed URLs with lastmod, changefreq, and priority when those fields are present. Page URLs are not fetched. Price $0.03 USDC. POST /api/v1/web-intelligence/sitemap-content-index. An unpaid call returns the x402 payment terms and does not run.

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": {
      "sitemapUrl": "<sitemapUrl>"
    },
    "name": "web-intelligence_sitemap-content-index"
  }
}

Input Schema

NameRequiredDescriptionDefault
sitemapUrlYessitemapUrl, string, length 8 to 2000. Required.

Output Schema

NameRequiredDescriptionDefault
kindNokind. String.
entriesNoentries. Array.
sourcesNosources. Array.
finalUrlNofinalUrl. String.
warningsNowarnings. Array.
entryKindNoentryKind. String.
httpStatusNohttpStatus. Number.
contentTypeNocontentType. String.
limitationsNolimitations. Array.
retrievedAtNoretrievedAt. String.
requestedUrlNorequestedUrl. String.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description goes further with the material behavior an agent cannot see in annotations: a $0.03 USDC price, that an unpaid call returns x402 payment terms and does not execute, and the concrete POST endpoint. It stops short of describing pagination or limits on large sitemap indexes, which is the remaining behavioral gap.

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?

Four short sentences, front-loaded with the action and result, then the exclusion, then the operational facts (price, endpoint, unpaid behavior). No sentence is redundant and nothing is buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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-shape detail is not required, yet the description still summarizes returned fields. For a one-parameter, paid, read-only endpoint, the description covers everything needed to call it correctly, including the payment precondition that would otherwise cause a silent no-op.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and there is only one parameter, so the baseline is already met. The description still adds meaning the schema does not: the URL may point to either a sitemap or a sitemap index, and it must be 'public', constraining what will be accepted beyond the bare https:// pattern.

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 concrete verb and resource ('Fetch one public sitemap or sitemap index') plus exactly what is returned (URLs with lastmod, changefreq, priority) and an explicit scope boundary ('Page URLs are not fetched'). That boundary is what separates it from the page-content siblings such as url-to-markdown, so an agent can route correctly without opening the schema.

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?

The 'Page URLs are not fetched' line and the 'one public sitemap' limit imply when this tool applies, and the payment note warns about a precondition. However, no sibling tool is named as the alternative for actually fetching page content, so the when-to-use-vs-alternatives guidance is inferred rather than stated.

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