Skip to main content
Glama
Sign In

AgentBIT

by app.agentbit
OverviewDiscussionsAdmin

Domain Dossier

agentbit.domain_dossier
Read-onlyIdempotent

Everything to vet a domain in one call: DNS records + email posture, RDAP registration/age/registrar, IP network/ASN/geo (from the resolved A record) and public threat-intel on the site. Four AgentBIT tools, merged. $0.015. Pay-per-call via x402 (USDC, Base).

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": "agentbit.domain_dossier"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesBare registrable domain, e.g. example.com (no scheme, no path)
_paymentNoOptional base64 x402 PAYMENT-SIGNATURE payload. Omit to receive payment requirements.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already carry the read-only/idempotent safety profile, so the description adds value by disclosing the merged scope of the call, the source of IP data (resolved A record), and the pay-per-call x402 pricing. It does not contradict any annotation.

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?

Two dense sentences deliver the full purpose, data categories, aggregation note, and pricing without wasted words. The key scoping statement is front-loaded and every clause earns its place.

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 high-complexity aggregator with no output schema, the description enumerates the returned data categories and the cost/payment model, which is enough to set expectations. It does not provide a sample response or failure modes, but the schema covers the one tricky parameter.

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 fully documents `domain` and `_payment`, including the bare-domain rule and the x402 payload semantics. The description adds no parameter-level detail beyond cost, making 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 opens with a concrete verb+resource ('vet a domain in one call') and enumerates the exact data categories returned: DNS, email posture, RDAP registration/age/registrar, IP/ASN/geo, and threat-intel. The 'Four AgentBIT tools, merged' phrase clearly separates it from narrower sibling tools by emphasizing aggregation.

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?

'Everything to vet a domain in one call' clearly frames when an agent should select this aggregate tool over single-purpose siblings. It does not explicitly name alternatives or exclusion conditions, so it stops short of a 5, but the intended usage context is unambiguous.

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

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