Skip to main content
Glama

XML sitemap builder

bpj_sitemap_xml_builder
Read-onlyIdempotent

Deduplicate up to 40 same-origin URLs and turn them into XML sitemap entries.

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": {
      "urls": "<urls>"
    },
    "name": "bpj_sitemap_xml_builder"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already declare this as a read-only, idempotent, non-destructive, closed-world operation. The description adds useful behavior beyond that: it deduplicates input, enforces a 40-URL cap, and requires same-origin URLs.

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?

It is a single efficient sentence with the core constraints front-loaded and no unnecessary wording.

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 simple one-parameter builder with no output schema, the description covers the essential transformation and input constraints. Minor gaps remain around exact output format and error behavior for invalid or over-limit URLs.

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?

The single parameter has 0% schema description coverage, though the schema title indicates one URL per line. The description compensates by stating the key semantic constraints: at most 40 URLs, same-origin only, and deduplication before conversion.

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?

The description uses a specific verb and resource: deduplicate URLs and turn them into XML sitemap entries. The scope constraints (up to 40, same-origin) make it distinguishable from sibling builders such as bpj_llms_txt_builder and bpj_article_structured_data.

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 transformation described, and the same-origin/40-URL limits act as practical constraints. However, there is no explicit guidance on when to choose this tool over alternatives or what prerequisites apply.

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.