robots_txt_validate
Validate robots.txt syntax and User-agent rules.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes |
ToolAPI
by org.toolapi
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- Added
TDQS
C2.6/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description bears full responsibility. It fails to mention whether the tool returns errors, warnings, or a simple pass/fail, nor does it describe any side effects or required permissions. The description only states the basic action.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness3/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that is front-loaded with the action verb. However, it is overly terse and could include more useful information without becoming verbose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (one input, no output schema), the description should provide enough context for an agent to understand the output format or validation behavior. It falls short by not describing what the validation result looks like or any examples.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has one required parameter 'text' with type string, but the description does not explain it at all. With 0% schema description coverage, the description should clarify what the parameter expects (e.g., full robots.txt content) but it does not.
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?
The description clearly states 'Validate robots.txt syntax and User-agent rules,' which includes the specific verb 'validate' and the resource 'robots.txt'. It distinguishes itself from sibling tools as no other tool deals with robots.txt files.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives. Although there are no sibling robots.txt tools, the description does not offer any context about appropriate usage scenarios or limitations.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
B3/5.0
Disambiguation5/5
Every tool has a clear, distinct purpose with thorough descriptions. Even closely related tools like base64_decode/encode and hash_md5/sha256 are easily differentiated by name and description.
Naming Consistency5/5
All tools follow a consistent lowercase_underscore naming convention, typically in a <domain>_<action> or <action>_<domain> pattern. There are no jarring deviations or mixed styles.
Tool Count1/5
193 tools is an extreme count, far beyond what any focused server needs. While each tool has utility, the sheer number creates a kitchen-sink effect that overwhelms agents and hinders discoverability.
Completeness4/5
Within each subdomain (JSON, cron, JWT, etc.), the coverage is exhaustive, covering validation, conversion, parsing, and more. Minor gaps exist (e.g., YAML-to-TOML conversion missing), but overall it is remarkably complete.