发现站点 URL 清单：优先 robots.txt / sitemap.xml，无站点地图时退化为入口页链接发现。
配合 scrape_url / crawl 使用：先 site_map 挑准页面，再精准抓取，省 credit。
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | 站点入口 URL（用于确定站点与域名） | |
| max_urls | No | 最多返回 URL 数（1-1000） |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It discloses key behaviors: prioritizing robots.txt/sitemap.xml and falling back to entry-page link discovery when no sitemap exists. It also hints at cost efficiency ('省 credit'). While it doesn't cover rate limits or error handling, the disclosed behavior is meaningful and non-generic.
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?
Two concise sentences deliver the core purpose, method, fallback behavior, and integration guidance. Every sentence earns its place, with no filler or repetition of schema content.
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?
Given the tool's moderate complexity, the description adequately covers how it discovers URLs and how to use it in conjunction with sibling tools. It lacks an explicit statement about return format, but that's not required given the absence of an output schema and the simplicity of the tool. Overall, it provides sufficient context for an agent to select and invoke it correctly.
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 100%: both 'url' and 'max_urls' are already described in the schema. The description adds no extra parameter-level detail beyond what the schema provides, so it receives the baseline score for high coverage.
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?
The description uses a specific verb+resource: '发现站点 URL 清单' (discover site URL list) and clearly states the method (robots.txt/sitemap.xml first, fallback to entry page links). It distinguishes itself from siblings like crawl and scrape_url by focusing on URL list discovery rather than full crawling or content extraction.
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?
The description explicitly advises using site_map before scrape_url or crawl to select target pages and save credits, providing clear when-to-use context. It doesn't mention when not to use it or alternatives beyond the stated sibling tools, but the cooperative workflow is well articulated.
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.
Each tool has a clearly distinct role: site_map discovers URLs, scrape_url fetches a single page, crawl fetches multiple pages, and extract returns structured JSON. The overlap between scrape_url and crawl is clearly addressed in descriptions by single vs multi-page, so an agent can easily select the right tool.
The names are mostly intuitive, with two verbs (crawl, extract) and two noun phrases (scrape_url, site_map). The mix of verb and noun forms is a slight inconsistency, but all names are lowercase with underscores, so the pattern is still predictable.
With only 4 tools, each serves a distinct step in the web data workflow: discovery, single-page fetch, multi-page crawl, and structured extraction. This is an appropriate scope for the server's purpose, neither too sparse nor overwhelming.
The tool set covers the full pipeline from discovering URLs (site_map) to fetching content (scrape_url, crawl) to extracting structured data (extract). There are no obvious gaps for the server's stated purpose of web data collection and transformation.