Skip to main content
Glama
Sign In
MWIE MCP Server

MWIE MCP Server

by tmolavi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

analyze_sitemap

Discover and parse URLs from an XML sitemap or sitemap index to inventory site pages for crawling, auditing, and SEO analysis.

Instructions

Discover and parse URLs from an XML sitemap or sitemap index.

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": {
      "sitemap_url": "<sitemap_url>"
    },
    "name": "analyze_sitemap"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_urlsNo
sitemap_urlYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations provided, the description carries the full behavioral burden, but it does not disclose how sitemap indexes are handled, whether fetching is recursive, how max_urls affects results, or what errors may occur. It only implies discovery and parsing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is concise and front-loaded with the core action and resource. It contains no wasteful wording, though it is perhaps too terse for the missing operational detail.

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?

An output schema exists, so the description need not explain return values. However, given zero schema description coverage and no annotations, the definition is missing key context about limits, behavior, and parameter meaning.

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

Parameters2/5

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

Schema description coverage is 0%, so the description should compensate for both parameters. While sitemap_url is implied by the resource, max_urls is never explained, including its default of 100 and whether it truncates results.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: discover and parse URLs from an XML sitemap or sitemap index. It is clear what the tool does, but it does not distinguish itself from sibling crawl tools such as crawl_domain or crawl_url.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. It only states the task, leaving the agent to infer selection from the name alone.

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

Deploy Server

Other Tools