Skip to main content
Glama

Robots check

robots_check
Read-onlyIdempotent

Check /robots.txt allowance, crawl-delay and sitemaps for a URL and optional crawler user-agent. $0.001 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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": {
      "url": "<url>"
    },
    "name": "robots_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYespublic http(s) URL
pathNopath to test
agentNocrawler token (default *)
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely new behavioral context the annotations cannot express: the per-call price, the accepted payment rails/currencies (USDC on Arc/Base/Solana, XNT on X1), and the fact that passing `payment` completes the purchase inside the tool call. It stops short of stating failure modes or what happens if payment is invalid.

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?

Three sentences, front-loaded with purpose, then cost, then the required call sequence. The currency/chain list is dense but load-bearing for payment decisions; nothing is redundant, though the parenthetical is the least essential clause.

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?

With no output schema, the description usefully names the three returned facts (allowance, crawl-delay, sitemaps), and the payment mechanic is fully explained for a paid tool. The main residual gap is error/expiry behavior for an invalid or already-consumed payment payload.

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?

Schema coverage is 100%, so the baseline is 3, and the description earns a bump by explaining the two-phase use of `payment` — the first call returns terms that must be signed before the second call carries the signed payload. That sequencing is meaning the schema cannot convey; `path` and `agent` remain covered only by the schema.

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 description opens with a specific verb and resource: check /robots.txt allowance, crawl-delay and sitemaps for a URL and optional crawler user-agent. That resource scope is distinct from every listed sibling (url_status, link_check, dns_records, security_headers, etc.), so an agent can select it without opening the schema.

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

Usage Guidelines4/5

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

It gives concrete operational guidance for the paid flow: call once without `payment` to get terms, sign with your own wallet, then call again with `payment` to complete the purchase. It does not name alternatives or state when a robots check is preferable to, say, url_status, so the when-not-to-use side is absent.

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