Skip to main content
Glama

Registry lookup

registry_lookup
Read-onlyIdempotent

Whether a domain is in CrawlCheck's registry and what it serves: llms.txt, agents.md, a media kit at /.well-known/media-kit.json, a reciprocity-tested entity graph, an AI access policy that names crawlers, and agent-callable surfaces. With no domain, returns the shelf counts across every measured site. A row exists because a fetch produced it; nothing here is self-reported and no payment moves a shelf.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "registry_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
shelfNoFilter the list to one shelf: llms, agents, mediakit, entity, aipolicy, agentapi
domainNoA bare domain. Omit for the corpus-wide shelf counts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely non-annotated context: rows exist only because a fetch produced them, nothing is self-reported, and paid placement cannot alter a shelf — provenance and trust properties an agent cannot get from structured fields. It stops short of saying what happens when a domain is absent from the registry.

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?

Two sentences, front-loaded with the core predicate and the served surfaces, followed by the no-argument behavior and the provenance guarantee. It is dense but each clause earns its place; the only friction is cryptic phrasing such as 'reciprocity-tested entity graph' and 'no payment moves a shelf', which is picturesque but not immediately parseable.

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 carries the burden of describing returns, and it does so by enumerating the six shelf types and the aggregate mode. For a read-only, two-parameter lookup this is largely sufficient, though it never states what a miss looks like versus a hit.

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% and both parameters carry their own descriptions, so the schema already does the heavy lifting and baseline 3 applies. The description reinforces the domain-omission branch and enumerates the shelf vocabulary, but that overlaps with the 'shelf' parameter's enum-like description rather than adding new syntax or format guidance.

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 names a specific resource and outcome: whether a domain is present in CrawlCheck's registry and which measured surfaces it serves (llms.txt, agents.md, media kit, entity graph, AI policy, agent-callable surfaces). That is far more than a restatement of the name. It stops short of explicitly contrasting itself with lookalike siblings such as scan_domain or resolve_domain, so an agent must infer the boundary.

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 only implied: the description distinguishes the two modes ('With no domain, returns the shelf counts across every measured site') which tells the agent the no-argument path is a corpus summary rather than a lookup. There is no explicit when-to-use versus scan_domain, corpus_state, or public_counts, and no stated prerequisite such as a domain being scanned first.

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.