Skip to main content
Glama

Nalvorn Checks

domain_posture

Read-only

Mail and DNS posture: A/AAAA, MX, SPF, DMARC policy, CAA, with a verdict Costs 0.005 USDC per call on Base (x402). Call it over HTTP with a PAYMENT-SIGNATURE header to actually run it.

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

Input Schema

NameRequiredDescriptionDefault
domainYesDomain name without scheme, for example example.com

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 readOnlyHint=true and openWorldHint=true, but the description adds two things annotations do not: a concrete price (0.005 USDC per call on Base via x402) and the payment-header requirement for execution. It stops short of describing failure modes, settlement behavior, or what the verdict contains.

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 capability scope and followed by the payment mechanics, with essentially no filler. Minor deduction for the unpunctuated run-together 'with a verdict Costs 0.005 USDC', which momentarily reads as a typo.

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 single-parameter read-only probe with no output schema, the description covers what is inspected, that a verdict is returned, and the payment prerequisite for invocation. What the verdict format looks like and how payment failures surface are the remaining gaps, but neither blocks a correct call.

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% for the single 'domain' parameter, including the 'no scheme' format note, so the schema already carries the semantics. The description adds nothing about the parameter, which makes the baseline 3 appropriate for a single fully documented input.

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 the exact resource and the specific record types inspected (A/AAAA, MX, SPF, DMARC policy, CAA) and says it produces a verdict, which is far more concrete than the tool name alone. It does not explicitly contrast with siblings like http_headers or tls_cert, but the enumerated scope makes the boundary inferable.

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?

There is no statement of when to choose this tool over full_report, site_ready, or tls_cert, so the alternative-selection guidance is absent. The one actionable directive — that it must be called over HTTP with a PAYMENT-SIGNATURE header to actually execute — is a useful operational prerequisite rather than a when-to-use rule.

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