Skip to main content
Glama
Dasistaiden

whed-tools

by Dasistaiden
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

crawl_website

Discover a website's pages and structure for WHED schema profiles, filtering out login, media, and unrelated content while crawling up to set depth and page limits.

Instructions

Crawl a website to discover its structure and pages.

Args:
    start_url: Starting URL
    max_pages: Maximum pages to crawl (default 50)
    max_depth: Maximum link depth (default 3)
    same_domain_only: Stay on same domain (default True)
    schema_filter: When True, only follow URLs whose path contains keywords
                   relevant to the WHED schema (about, contact, course, program,
                   faculty, etc.). Skips login pages, media, and unrelated content.
                   Recommended for institution websites.
    save_path: Optional file path to save the site map as JSON (e.g. "C:/Users/me/Desktop/sitemap.json").
               If a directory is given, a timestamped filename is generated automatically.

Returns:
    Site map with discovered pages and statistics

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
max_depthNo
max_pagesNo
save_pathNo
start_urlYes
schema_filterNo
same_domain_onlyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose real behavior: schema_filter skips login pages, media and unrelated content, and save_path auto-generates a timestamped filename when given a directory. It omits important operational traits such as rate limiting/politeness, robots.txt handling, authentication needs, and whether the crawl is strictly read-only.

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 opening sentence front-loads the purpose, and the Args/Returns docstring layout is scannable and efficient. The Returns line is slightly redundant given an output schema exists, but overall it is well-sized with no padding.

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 six-parameter crawl tool with an output schema and no annotations, the description covers purpose, every parameter, and the notable filtering/saving behaviors. The remaining gap is operational safety context (read-only nature, throttling, domain restrictions beyond same_domain_only), which slightly reduces confidence.

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 description coverage is 0%, so the description must compensate, and it does: all six parameters are documented with defaults and semantics, including the non-obvious schema_filter keyword behavior and the directory-vs-file behavior of save_path. Only start_url and the two numeric limits get minimal treatment, but nothing is left ambiguous.

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?

States a specific verb and resource ('Crawl a website to discover its structure and pages'), which is clear and distinct from pure content extraction. However, it never differentiates itself from close siblings like scrape_url or batch_scrape, so an agent must infer that this tool maps the site rather than fetching content.

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

Usage Guidelines3/5

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

Usage is implied by the crawl-and-discover framing, and schema_filter carries a 'Recommended for institution websites' hint, which is useful context. But there is no explicit statement of when to use this over scrape_url/batch_scrape, nor any prerequisites or exclusions.

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