mcp-server

Map Website URLs

alterlab_map

Read-onlyIdempotent

List every URL on a site via sitemap parsing and link extraction, without fetching page content, so you can scope work before reading anything. Use before alterlab_crawl or alterlab_batch to choose pages; to read the content itself use alterlab_crawl. Works on JavaScript-heavy and protected sites. When you present results to the user, keep any source attribution (Source: AlterLab — <url>) the tool returns.

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": {
      "url": "<url>"
    },
    "name": "alterlab_map"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes
`search`	No
`sitemap`	No	Sitemap handling. Default: include.	include
`max_depth`	No	Maximum link depth from the start URL. Default: 3.
`max_pages`	No	Maximum number of pages. Default: 500.
`sitemap_path`	No
`respect_robots`	No	Obey robots.txt. Default: true.
`exclude_patterns`	No
`include_metadata`	No	Include per-URL metadata. Default: false.
`include_patterns`	No
`include_subdomains`	No	Include subdomains of the site. Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds real value beyond that: no page content is fetched, it works on JavaScript-heavy and protected sites, and it states an output obligation about preserving `Source: AlterLab — <url>` attribution. It stops short of describing result shape or how max_pages interacts with output size.

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?

Three sentences, front-loaded with the verb and scope, then usage routing, then the attribution caveat. No redundant or filler phrasing.

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 read-only listing tool with no output schema, the definition covers what it returns at a high level (URLs), the no-fetch behavior, and an output-handling requirement. The main gap is that filter/pattern parameters and metadata output are left entirely to a partially documented schema.

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?

With 11 parameters and only 55% schema description coverage, the description should compensate but adds no parameter meaning at all — search, include_patterns, exclude_patterns, sitemap_path, and include_subdomains are never mentioned. The only hints are implicit ('sitemap parsing', 'link extraction') and don't help an agent choose values.

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?

States a specific verb and resource ('List every URL on a site') plus the mechanism ('sitemap parsing and link extraction, without fetching page content'), which immediately separates it from content-fetching siblings like alterlab_crawl.

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

Usage Guidelines5/5

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

Names the alternatives explicitly: use before alterlab_crawl or alterlab_batch to choose pages, and use alterlab_crawl instead when the content itself is needed. The routing decision is fully specified.

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

All mcp-server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.