url_normalizerNormalizes and deduplicates a list of URLs. x402 payment required (testnet USDC, Base Sepolia).
| Name | Required | Description | Default |
|---|---|---|---|
| urls | Yes | 正規化したいURLの配列 | |
| payment | No | x402 payment payload (base64 JSON), signed EIP-712 exact/transferWithAuthorization. Omit on the first call — the tool will return payment requirements (accepts[]) as an error result. | |
| forceHttps | No | ||
| stripParams | No | ||
| keepTrailingSlash | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
没有 annotations，因此描述需承担全部行为披露责任。'Normalizes and deduplicates' 过于笼统，未说明 URL 会如何被修改、是否有副作用、支付失败时的行为等。
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?
两句话简洁直接，第一句概括功能，第二句补充支付要求，没有冗余内容，但缺少必要扩展。
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?
这是一个有 5 个参数、无输出 schema、无兄弟工具的工具，而描述仅两句话，未提供返回格式、使用流程或参数间关系等信息。
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 覆盖率仅 40%，仅 urls 参数有描述，而 forceHttps、stripParams、keepTrailingSlash、payment 在描述中未被说明。描述完全依赖 schema 本身，没有补充任何参数使用细节。
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?
描述以 'Normalizes and deduplicates a list of URLs' 明确指出了操作和对象，并且附加了支付要求，这提供了基本用途。不过 'url_normalizer' 与标题相同，缺少更具体的功能说明，也没有兄弟工具可区分。
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?
描述没有说明何时使用此工具、何时不使用，也没有提及前置条件（如首次调用需省略 payment 参数）。虽然提供了'需要支付'的信息，但这并非使用指南。
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.
Only one tool exists, so there is no possibility of confusing it with others. The tool's purpose is clearly stated and unique within this server.
The single tool uses a clean snake_case convention with a descriptive name (url_normalizer). With only one tool, there are no inconsistencies in naming patterns.
A single tool is generally too few to constitute a well-rounded server, even if the scope is narrow. The tool count falls outside the typical 3-15 range and feels minimal for any meaningful workflow.
The server only offers URL normalization and deduplication, with no supporting operations like validation, parsing, or bulk handling variations. This leaves the tool surface very thin and may require additional external steps for common use cases.