DS4AI MCP

generate_sitemap

Create a sitemap.xml from a list of canonical URLs, accepting strings or objects with loc, lastmod, changefreq, and priority. Use to generate findability metadata for web surfaces.

Instructions

Serialize a sitemap.xml from a list of canonical URLs (strings, or objects with loc, lastmod, changefreq, priority).

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

Input Schema

Name	Required	Description	Default
`urls`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 21, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It states the transformation (serialize) but omits behavioral details such as output format specifics (XML declaration, encoding), error handling for invalid URLs, or whether it validates input. The operation is simple and read-only in nature, so a score of 3 reflects adequate disclosure for a pure function.

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 sentence, front-loaded with the main purpose and input details. There is no redundancy or filler, making it highly concise and structured.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple with one parameter, and the description covers the input adequately. However, there is no output schema and the description does not clarify the exact return format beyond implying a serialized XML string (e.g., whether it includes XML declaration, pretty printing, or encoding). This gap in output specification keeps it from being fully complete.

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 schema provides zero coverage and only defines 'urls' as an array of strings or objects. The description compensates well by explicitly listing accepted formats: strings or objects with loc, lastmod, changefreq, priority. This adds meaningful semantics 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?

The description clearly states the tool serializes a sitemap.xml from a list of canonical URLs, distinguishing it from sibling tools like generate_robots and generate_head. It uses a specific verb (Serialize) and resource (sitemap.xml) with input format details.

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 description implies usage for generating sitemap.xml but offers no explicit guidance on when to use this tool versus alternatives like generate_robots or generate_head. There is no when-not-to-use or alternative mention, so it only meets the implied usage level.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server