Short catalog of common HTTP status codes.
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | HTTPS URL to normalize or cite | |
| host | No | Public hostname | |
| json | No | JSON text to validate; discarded after the check | |
| zone | No | IANA timezone name |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
无注解，且描述未透露任何行为特性，如查询方式、返回结构、副作用或错误处理，完全依赖猜测。
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?
在无注解、无输出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覆盖度为100%，但描述未说明参数如何与状态码目录关联，如url、host、json、zone与HTTP状态码的关系，语义不明确。
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?
描述'Short catalog of common HTTP status codes'仅说明这是一个状态码目录，但未指明该工具的具体功能（如查询、验证、转换等），动词缺失，无法与兄弟工具区分。
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?
描述未说明何时使用此工具，也未提及任何替代工具或排除条件，上下文信息完全缺失。
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.
Most tools have distinct outputs, but there is real overlap: http-404 is a subset of status-catalog, timezone overlaps utc-time, and citation/normalize-url/domain-shape all parse URLs in slightly different ways. The descriptions clarify intended uses, so an agent can usually pick correctly, but the boundaries are not crisp.
Names are all lowercase kebab-case, which provides a surface-level consistency, but the structural pattern is mixed: single nouns, noun-noun compounds, and imperative verb-noun forms. This makes the naming scheme less predictable than a uniform verb_noun or noun-based convention.
Eleven tools is within a reasonable numeric range, but the set is not tightly scoped: URL/HTTP tools are mixed with timezone, JSON, and compatibility tools. A more focused HTTP utility server could easily justify fewer or more cohesive tools.
The inferred domain is URL/HTTP inspection, and the set covers normalization, status codes, and robots, but it lacks obvious related operations such as HTTP headers, redirects, or URL decoding. The presence of unrelated time and JSON tools makes the surface feel arbitrary rather than deliberately complete.