Skip to main content
Glama
Sign In

automaton

by uk.firstmention.api
OverviewDiscussionsAdmin

websearch__crawlcheck

May I lawfully fetch this URL? Fetches robots.txt and returns an allow/disallow verdict for the given URL and user-agent, with the matched rule, crawl-delay and sitemaps. Only /robots.txt is read; no page content is fetched. Price: $0.01 per call in USDC on Base (eip155:8453), paid with x402 in params._meta["x402/payment"]. HTTP: GET https://api.firstmention.uk/s/websearch/crawlcheck

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": "websearch__crawlcheck"
  }
}

Input Schema

NameRequiredDescriptionDefault
uaNoUser-agent to evaluate (default *)
urlYesAbsolute http(s) URL to check

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so well: it discloses that only /robots.txt is read, no page content is fetched, and the response includes the verdict, matched rule, crawl-delay, and sitemaps. It also states pricing and the x402 payment mechanism, which are important operational details.

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

Conciseness5/5

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

The definition is front-loaded with the core question, followed by return behavior, scope, price/payment, and endpoint. Every sentence contributes useful information with no redundant restatement.

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?

For a two-parameter, read-only compliance tool with no output schema and no annotations, the description covers what is read, what is returned, what is not fetched, and how payment works. Nothing essential for correct invocation is missing.

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 100%, so the schema already explains both url and ua. The description mentions the URL and user-agent being evaluated, but adds no syntax or format detail beyond what the schema provides, making the baseline 3 appropriate.

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 states a specific verb and resource: fetches robots.txt and returns an allow/disallow verdict for a URL and user-agent. It also clearly distinguishes this tool from content-fetching siblings by saying only /robots.txt is read and no page content is fetched.

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?

The opening question, "May I lawfully fetch this URL?", makes the intended use case clear: compliance checking before crawling or fetching. It does not explicitly name alternatives or when-not-to-use conditions, but the context is strong enough for correct selection.

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

All automaton 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