Skip to main content
Glama
Sign In

Burs-IA Utils

by io.github.soyeladice-svg
OverviewDiscussionsAdmin

Acceso de rastreadores de IA

robots-ai-crawlers
Read-onlyIdempotent

Informa, para un robots.txt dado y 21 rastreadores de IA conocidos (GPTBot, ClaudeBot, Google-Extended…), si una ruta está permitida y si la decisión viene de un grupo específico. Cuándo: hay que leer, construir o revisar con exactitud una URL, una cabecera HTTP, un token, una versión, un rango de IP, un documento HTML o Markdown o un archivo para agentes. No para: decidir si un agente puede acceder a una ruta según un robots.txt dado (robots-txt-check). Efectos secundarios: ninguno (solo lectura, sin red, sin estado guardado). Determinista: la misma entrada da la misma salida. Límites: entrada JSON de hasta 64 KB, 1 s por llamada, resultado de hasta 1 MB.

EN: Reports, for a given robots.txt and 21 known AI crawlers and agent fetchers (GPTBot, ClaudeBot, Claude-User, Google-Extended, PerplexityBot, CCBot…), whether a path is allowed and whether the decision comes from a bot-specific group. [EN completo / full EN: inputSchema.description]

Input Schema

NameRequiredDescriptionDefault
pathNoPath to test (string; optional; default "/"; up to 4096 chars)./
robots_txtYesrobots.txt content (string; required).

Output Schema

NameRequiredDescriptionDefault
botsNo
pathNo
allowed_countNo
blocked_countNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / robots_txt / examples
      Added value: +[
+  "User-agent: *\nAllow: /\n\nUser-agent: GPTBot\nUser-agent: CCBot\nDisallow: /"
+]
  2. Changed1 schema field changed
    • addedInput schema / description
      Added value: +"EN: Reports, for a given robots.txt and 21 known AI crawlers and agent fetchers (GPTBot, ClaudeBot, Claude-User, Google-Extended, PerplexityBot, CCBot…), whether a path is allowed and whether the decision comes from a bot-specific group. When: a URL, HTTP header, token, version string, IP range, HTML or Markdown document or agent-readiness file has to be parsed, built or checked exactly. Not for: deciding whether a user agent may fetch a path under a supplied robots.txt (robots-txt-check). Side effects: none (read-only, no network access, no stored state). Deterministic: the same input gives the same output. Limits: JSON input up to 64 KB, 1 s per call, result up to 1 MB."
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

The description adds significant behavioral context beyond the annotations, detailing its side effects (none: read-only, no network), deterministic nature, and technical limits (input/output size, latency).

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?

Despite being quite dense due to the high amount of required information, the information is well-organized, front-loading the purpose and distinguishing usage scenarios before detailing behavioral limits.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity and the similarity to other string/parsing tools in the ecosystem, this description is exceptionally complete. It provides functional logic, scope, and performance characteristics that an agent needs to select it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema coverage, the description is mostly complementary. It adds high-value domain context by identifying the specific types of agents (AI crawlers) and the operational context for the required `robots_txt` content.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The tool clearly states its purpose: reporting path permissibility for a given robots.txt and 21 known AI crawlers. It clearly distinguishes itself from other related tools by mentioning its role in parsing and decision-making (or lack thereof in the sibling).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides explicit guidance on when to use the tool: when reading/parsing URLs, HTTP headers, tokens, or agent readiness files. Crucially, it specifies when NOT to use it (i.e., for a simple robots-txt-check).

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

All Burs-IA Utils toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources