Skip to main content
Glama

BRAINIAC Email & Domain Intelligence

Report domain registration signals

email-domain_reputation-signals

Return the RDAP registration date and whether a DNSSEC DS record is published. The reputation verdict stays unavailable because no unauthenticated reputation feed is queried. Price $0.04 USDC. POST /api/v1/email-domain/reputation-signals. Unpaid calls return 402 and do not run.

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": "email-domain_reputation-signals"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/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 the price ($0.04 USDC), the endpoint method/path, and that unpaid calls return 402 without executing. It also pre-empts a false expectation by explaining why no reputation verdict is returned. It omits whether the POST is effectively read-only and any rate/timeout behavior, which is why this is not a 5.

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?

Front-loaded with the returned values, which is the right priority, and there is no filler. The operational tail (price, endpoint, 402 behavior) is dense but each clause carries distinct information. The 402 sentence could merge with the price sentence for tighter flow.

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?

A single-parameter lookup with no output schema and no annotations still needs its return fields and failure modes explained, and both are covered, including the explicit negative case (no reputation verdict). What remains thin is the domain input format, which is the only thing an agent could plausibly get wrong when calling it.

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?

Only one parameter exists and it is self-evident (a domain) given the tool's scope, and schema coverage is 0%, so the schema adds nothing. The description doesn't specify accepted domain format (bare name vs URL, IDN handling) despite maxLength 253. A 3-param or ambiguous case would score lower, but single-parameter simplicity keeps this defensible.

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?

Specific verb and resources: "Return the RDAP registration date and whether a DNSSEC DS record is published." That tells an agent exactly what comes back. It doesn't distinguish itself from the sibling email-domain_registration-lookup, which plausibly returns overlapping registration data, so the boundary is left to inference.

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?

The description narrows scope by stating the reputation verdict is unavailable and that no unauthenticated reputation feed is queried, which implicitly says when not to use it for scoring. It gives no explicit when-to-use guidance and names no alternative among the nine siblings, so selection is only implied.

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