Skip to main content
Glama

Tools for Agents

by io.github.max124vip-dev
OverviewDiscussionsAdmin

robots_parse

Parse robots.txt rules

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesSite URL
timeoutNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / properties / args
      Removed value: -{
-  "description": "Tool arguments",
-  "properties": {
-    "text": {
-      "description": "Primary input text",
-      "type": "string"
-    }
-  },
-  "type": "object"
-}
    • addedInput schema / properties / timeout
      Added value: +{
+  "default": 15,
+  "type": "integer"
+}
    • addedInput schema / properties / url
      Added value: +{
+  "description": "Site URL",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[]New value: +[
+  "url"
+]
  2. Added

TDQS

C2.7/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that it parses rules, with no mention of network requests, timeout behavior, return value shape, or potential side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no filler, which is efficient. However, it is so terse that it sacrifices necessary context, making it concise but not fully appropriately sized.

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?

With no output schema or annotations, the description fails to convey what the parsed output looks like or how errors are handled. For a network-triggered tool with a timeout parameter, this leaves significant gaps.

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?

Schema coverage is 50%: 'url' has a generic 'Site URL' description and 'timeout' has none. The description adds no additional meaning beyond what the schema already states, leaving timeout semantics entirely unexplained.

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 uses a specific verb ('parse') and resource ('robots.txt rules'), clearly identifying the tool's function. It naturally distinguishes from sibling parsers like sitemap_parse by naming robots.txt explicitly, though it omits any detail about the output format or scope.

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?

The description provides no guidance on when to use this tool versus alternatives such as crawl or sitemap_parse. There is no mention of use cases, prerequisites, or exclusion scenarios.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Tools for Agents toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources