Skip to main content
Glama

AI Crawler Permission Check

Is this user-agent allowed on a path

check_user_agent
Read-onlyIdempotent

Whether a given crawler user-agent token may fetch a path on a domain according to robots.txt.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site": "<site>",
      "user_agent": "<user_agent>"
    },
    "name": "check_user_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo
siteYes
user_agentYes

Output Schema

NameRequiredDescriptionDefault
allowedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds that the result is based on robots.txt, which explains the source of truth, but it does not describe matching behavior, live fetching, caching, or other operational traits beyond the annotations.

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 definition is a single front-loaded sentence with no wasted wording. It is efficient, though its brevity leaves important operational details unstated.

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

Completeness4/5

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

An output schema exists, so return values need not be explained. For a simple three-parameter robots.txt check, the description covers the core purpose and source of truth, though it omits optional-path behavior and matching details that would help an agent invoke it confidently.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must carry parameter meaning. It does identify the three conceptual inputs—site/domain, user-agent token, and path—but it does not clarify the optional path default, accepted formats, or matching semantics for the user-agent token.

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 states a specific check: whether a crawler user-agent token may fetch a path on a domain according to robots.txt. It clearly identifies the resource and decision being made, though it does not explicitly distinguish this tool from the sibling check_ai_crawlers.

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?

Usage is only implied by the purpose: an agent can infer this is for robots.txt permission checks. There is no explicit guidance on when to use it versus check_ai_crawlers, no prerequisites, and no exclusions.

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.

Resources