Skip to main content
Glama

domain_intel__policy

AI-crawler policy for a domain: robots.txt verdict per AI bot (GPTBot, ClaudeBot, CCBot, Google-Extended and 16 more), llms.txt presence and sitemap. GET /s/domain-intel/policy?domain=example.com 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/domain-intel/policy

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": {
      "domain": "<domain>"
    },
    "name": "domain_intel__policy"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain or URL, e.g. example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does well: it discloses the per-call cost ($0.01 USDC on Base, eip155:8453), the exact payment location in params._meta["x402/payment"], the HTTP method and URL, and roughly what the response contains. It does not cover error behavior, rate limits, or what happens on unpaid calls, which keeps it out of 5 territory.

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?

Content is front-loaded with the purpose in the first sentence, followed by compact payment and transport lines. It is dense but every line carries information; the only mild redundancy is repeating the domain in the example URL already present in the schema.

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?

For a one-parameter, read-style tool with no output schema, the description supplies the essentials an agent needs to invoke it: what it returns, what it costs, and where the payment proof goes. Only the failure modes and the exact response shape for the 19 bots are left implicit, which is minor at this complexity.

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 coverage is 100% and the single domain parameter is already documented with a format example, so the description only echoes it via the example.com query string. No additional semantics (input normalization, URL vs bare domain handling) are added beyond 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 first clause names the verb and resource precisely: 'AI-crawler policy for a domain', then enumerates the returned artifacts (robots.txt verdict per named AI bot, llms.txt presence, sitemap). That is specific enough to separate it from siblings like domain_intel__dns or domain_intel__lookup without opening any schema.

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

Usage Guidelines3/5

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

Usage is implied by the resource description — an agent can infer 'use this when you need to know whether AI crawlers are allowed on a domain' — but there is no explicit when-to-use, when-not, or reference to an alternative sibling. The pricing and endpoint lines are operational details, not selection guidance.

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