List child sitemap URLs from Pristine Marketplace's /sitemap.xml index, with inferred sitemap types, to map site content for crawling or indexing.
List Pristine Marketplace sitemaps. Returns child sitemap URLs from Pristine Marketplace's (https://www.pristinemarketplace.com) /sitemap.xml index with inferred sitemap types. The storefront URL is fixed server-side.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of behavioral disclosure. It does disclose the source URL, that it returns child sitemap URLs, that types are inferred, and that the storefront URL is fixed server-side. However, it does not address whether the operation is read-only, rate limits, pagination, or failure behavior, leaving some behavioral context implicit.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is compact and front-loaded, with the main verb and resource in the first sentence followed by concrete technical details. The first sentence slightly echoes the tool name, but the remaining sentences earn their place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a no-parameter, no-output-schema listing tool, the description gives sufficient context: source, output shape, type inference, and fixed URL. The main gap is not addressing the closely related sibling tool, which could help an agent choose correctly in a large tool catalog.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, which gives a baseline of 4. The description adds meaningful context by stating 'The storefront URL is fixed server-side,' explaining why no URL parameter is needed and preventing an agent from searching for one.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb and resource: 'List Pristine Marketplace sitemaps' and explains the output as child sitemap URLs from the `/sitemap.xml` index with inferred types. It is clear about what the tool does, though it does not explicitly distinguish itself from the closely named `pristine_marketplace_sitemap_urls` sibling.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance about when to use this tool versus alternatives, especially the similarly named `pristine_marketplace_sitemap_urls` sibling. The fixed-server-side note is helpful but does not tell an agent when this tool is the right choice or when another sitemap-related tool should be preferred.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.