Get information about an HTTP status code.
| Name | Required | Description | Default |
|---|---|---|---|
| code | Yes | HTTP status code |
| Name | Required | Description | Default |
|---|---|---|---|
| code | Yes | ||
| name | Yes | ||
| category | Yes | ||
| description | Yes |
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?
The description implies a read-only operation ('Get information'), but with no annotations provided, it lacks explicit behavioral disclosure. It does not mention any side effects or safety details, which is a gap given the absence of annotations.
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?
The description is a single, front-loaded sentence with no unnecessary words. It efficiently conveys the tool's purpose.
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?
For a simple lookup tool with an output schema, the description is minimally adequate. However, it does not hint at what kind of information is returned (e.g., category, description), which would improve completeness.
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?
The single parameter 'code' is fully described in the input schema ('HTTP status code'), so the description adds no new meaning beyond what the schema already provides. Baseline score of 3 is appropriate.
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 clearly states the verb 'Get information' and the resource 'HTTP status code', making the tool's purpose unambiguous. It distinguishes from sibling 'http_method_info' by focusing on status codes, though it doesn't explicitly differentiate.
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 provides no guidance on when to use this tool or how it compares to alternatives like 'http_method_info'. There is no mention of prerequisites or limitations.
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.
Many tools have overlapping purposes, such as multiple random generators (random_integer, random_number), duplicate hashing functions (hash_md5, md5_checksum), and near-identical tools (compare, compare_2, compare_decimals). The sheer number of tools and lack of clear boundaries make it difficult for an agent to differentiate.
Naming is highly inconsistent. There are duplicate tools with different names (camel_case vs to_camel_case, slug vs slugify), arbitrary suffixes like '_2', and mixing of patterns (e.g., generate_password vs password_entropy). No clear convention is followed.
With 572 tools, the server is massively overpopulated for any coherent purpose. It includes trivial endpoints (true_endpoint, null, hello_world) and numerous duplicates, far exceeding a well-scoped utility set.
While the server covers many domains (math, strings, dates, colors, etc.), the presence of duplicate and trivial tools indicates a lack of thoughtful curation. There are gaps in basic operations (e.g., no dedicated file or network tools), and many tools are redundant.
