Skip to main content
Glama
RapierCraft

alterlab-mcp-server

by RapierCraft

alterlab_map

Discover all URLs on a website by parsing sitemaps and extracting links. Use patterns to scope discovery and search to rank by relevance.

Instructions

Discover all URLs on a website via sitemap parsing and link extraction. No JS rendering, no content scraping — pure lightweight URL discovery. Costs $0.001 per call regardless of how many URLs are found. Returns a flat list of URLs with source (sitemap/link) and depth. Use include_patterns/exclude_patterns to scope discovery to specific sections. Use search to rank URLs by relevance to a query. Use include_metadata=true to also fetch page titles and descriptions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesStarting URL for site discovery
max_pagesNoMaximum URLs to discover
max_depthNoLink-following depth (0 = start page + sitemap only)
include_patternsNoGlob patterns — only include URLs whose path matches at least one (e.g., ['/docs/*'])
exclude_patternsNoGlob patterns — exclude URLs whose path matches any (e.g., ['/tag/*', '/page/*'])
searchNoQuery to filter and rank discovered URLs by relevance (returns relevance_score per URL)
sitemapNoSitemap handling: include (parse sitemaps + follow links), skip (links only), only (sitemap URLs only)include
include_metadataNoFetch title and meta description for each URL via lightweight GET (adds latency)
include_subdomainsNoInclude URLs from subdomains of the target domain
respect_robotsNoRespect robots.txt directives
Behavior5/5

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

No annotations provided, so description fully discloses behavior: no JS rendering, no content scraping, cost per call, output format (flat list with source and depth), and latency added by include_metadata. No contradictions.

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?

Description is well-structured, front-loaded with purpose, then cost, output, and parameter tips. Slightly long but each sentence adds information, no redundancy.

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

Completeness5/5

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

Given 10 parameters and no output schema, the description sufficiently covers tool behavior, parameter usage, output format, cost, and caveats. Complete for an API tool.

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?

Schema coverage is 100%, baseline 3. Description adds value by explaining glob patterns for include/exclude, relevance_score for search, and sitemap enum values, going beyond schema descriptions.

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?

Description clearly states the tool discovers all URLs on a website via sitemap parsing and link extraction. It uses specific verb (discover), resource (URLs), and method, distinguishing it from siblings like crawling or scraping.

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

Usage Guidelines4/5

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

Provides guidance on using include_patterns/exclude_patterns to scope discovery, search to rank by relevance, and include_metadata for titles/descriptions. Does not explicitly state when not to use, but context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/RapierCraft/alterlab-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server