Skip to main content
Glama

grid402_domain_audit

Read-onlyIdempotent

Consolidated Domain Audit bundle (DNS + TLS/SSL + BGP/ASN) with risk score (0.0150 USDC / 3 credits).

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

Input Schema

NameRequiredDescriptionDefault
domainYesDomain name to audit (e.g. base.org).
payment_tx_hashNoOptional txHash on Base Mainnet, Session Pass token (pass_g402_...), EIP-3009 base64 payload, or demo for Sandbox.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / domain / description
      Added value: +"Domain name to audit (e.g. base.org)."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description's added value is the cost disclosure '0.0150 USDC / 3 credits' and the fact that results roll up into a risk score. It still doesn't say what happens on payment failure or what the response contains beyond the score.

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?

One sentence, front-loaded with what the tool does, then its components, its output and its cost. Nothing is redundant or buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 only says 'risk score'. An agent cannot tell whether the underlying DNS records, TLS certificate details and BGP/ASN data are also returned or whether only the aggregate score is produced.

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 the schema itself explains the domain format and the four accepted payment_tx_hash forms. The description adds no parameter-level meaning, so the baseline 3 applies; the price mention marginally contextualizes why payment_tx_hash exists.

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?

Names a specific resource (Domain Audit) and enumerates exactly what the bundle covers (DNS + TLS/SSL + BGP/ASN) plus the composite output (risk score). The word 'Consolidated' implicitly distinguishes it from the single-purpose siblings grid402_dns, grid402_ssl and grid402_asn, though it never names them.

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: 'bundle' suggests this is the all-in-one option when several domain signals are needed, but there is no explicit when-to-use, no statement that it replaces calling the individual DNS/SSL/ASN tools, and no prerequisites beyond a domain.

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