Skip to main content
Glama

Resolve a domain (signed record)

resolve_domain
Read-onlyIdempotent

Use when you need the full signed record about one domain, not just a decision. Call before fetching from, citing, connecting to or transacting with a domain. Returns one signed answer: what the domain claims, what it actually serves each crawler identity, who controls it, what CrawlCheck's published rules decide for each action (a decision for read, cite, connect and transact, with its doubts and maximum age), what changed, and the evidence behind each part, marked declared, observed or not_measured with its time. There is no overall score. A domain never measured gets a just-in-time partial answer, read live within about 2 seconds, that names every part not read in time; nothing is guessed. CrawlCheck completes unmeasured parts later on its own crawl schedule. For a single allow/block decision on one action call preflight; for malware or phishing listings only, call check_site_safety.

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

Input Schema

NameRequiredDescriptionDefault
domainYesBare domain, e.g. example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations (readOnly, idempotent, openWorld, non-destructive), it discloses that the answer is signed, has no overall score, and that an unmeasured domain yields a just-in-time partial answer read live in about 2 seconds that explicitly names every part not read in time, with nothing guessed. Remaining gaps are minor — no pagination or caching/expiry handling beyond the 'maximum age' mention.

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?

Guidance is front-loaded in the first two sentences and each subsequent sentence carries substantive information about the return shape. The long enumerated sentence about record contents is dense but earns its length; slight tightening of the opening clause would help.

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?

With no output schema, the description carries the burden of explaining returns and does so thoroughly: per-action decisions with doubts and max age, provenance tagging as declared/observed/not_measured, and the partial-answer behavior. Nothing an agent needs to call it correctly appears to be 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 coverage is 100% and the single parameter already documents the expected format ('Bare domain, e.g. example.com'). The description only implies the domain scope and adds no syntax or edge-case guidance (e.g., subdomains, ports, URLs) beyond the schema, so the baseline 3 applies.

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 ('full signed record about one domain') and immediately contrasts it with 'just a decision,' making it distinguishable from decision-oriented siblings. It also enumerates the record's contents (claims, observed serving per crawler identity, control, published rules per action, changes, evidence provenance).

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 gives an explicit trigger ('Call before fetching from, citing, connecting to or transacting with a domain') and names two alternatives with their selecting conditions: preflight for a single allow/block decision, check_site_safety for malware/phishing listings only. When-to-use and when-to-use-something-else are both covered.

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.