List site URLs for a domain.
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": {
"payload": "<payload>"
},
"name": "site-map"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| payload | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description carries the full behavioral burden, and it discloses almost nothing: it implies a read-only listing but never mentions whether it fetches the domain's sitemap.xml, crawls links, is rate-limited, or respects robots. The parameter-driven behaviors (sitemap_mode include/skip/only, subdomain expansion, query-parameter collapsing, 1000-URL cap) are entirely invisible.
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?
One front-loaded sentence with no wasted words, but the terseness here reflects under-specification rather than discipline: a tool with six nested options and an enum gets no structural elaboration despite ample room.
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?
An output schema exists so return values need no explanation, but a tool with a required wrapper object, a mode enum, and subdomain/query-normalization flags needs far more than one sentence. An agent could not correctly set sitemap_mode or predict result scope from this description alone.
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?
Schema description coverage is 0%, so the description must compensate, but it only gestures at 'domain' and 'site URLs' — loosely hinting at the url field and sitemap semantics. The six nested payload options, especially the sitemap_mode enum and include_subdomains/ignore_query_parameters toggles that materially change the result set, are never explained anywhere.
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?
States a concrete verb+resource: 'List site URLs for a domain.' An agent can tell this produces a URL inventory rather than a full audit (site-audit) or a page fetch (page-extract). However, it does not explicitly contrast itself with the closest siblings, so it stops short of a 5.
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 when-to-use guidance, no prerequisites, and no named alternative. The description never says why an agent would choose site-map over site-audit, page-extract, or search-results, leaving selection entirely to inference from the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.