Skip to main content
Glama

Sitesy Website Intelligence

DNS and certificate posture

dns_posture
Read-onlyIdempotent

DNS and certificate posture report for one domain, built for IT providers: mail authentication (SPF, DMARC, DKIM), the DNSSEC signal, certificate basics, and findings ranked most serious first. Costs 0.01 USDC per call. The caller pays per call in USDC on Base through x402: the first call returns the payment requirements, and an x402 aware MCP client signs and retries automatically.

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

Input Schema

NameRequiredDescriptionDefault
domainYesA domain name, for example example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, open-world), so the bar is lower, yet the description adds critical behavior the annotations cannot express: a 0.01 USDC per-call cost, payment on Base via x402, and — importantly — that the first call returns payment requirements and an x402-aware client must sign and retry. Without that, an agent would misread the first response as a failure.

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 sentences, no waste: the first covers purpose and report contents, the second covers cost and the payment/retry mechanics. The most decision-critical fact for an agent — that payment is required and a retry follows — is stated plainly in the second sentence.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool with no output schema, the description is complete: it lists the report's sections, notes findings are severity-ranked, and explains the payment handshake that would otherwise cause a wrong conclusion on the first response. Nothing needed to invoke it correctly is missing.

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?

The schema has a single, fully documented parameter (domain, with format example and length bounds) at 100% coverage, so the schema carries the load and the baseline of 3 applies. The description confirms the tool accepts exactly one domain but adds no syntax or edge-case meaning (e.g., IDN, subdomain, trailing dot handling) beyond the schema.

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 states a specific verb and resource — a DNS and certificate posture report for one domain — and enumerates the report's contents (SPF, DMARC, DKIM, DNSSEC, certificates, ranked findings), so the agent knows exactly what it gets. It does not explicitly distinguish itself from the sibling dns_lookup or domain_profile, leaving overlap 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?

"Built for IT providers" gives a loose audience context, and the enumeration of report contents implies the use case (full posture assessment rather than a single query). However, there is no explicit statement of when to pick this over dns_lookup or domain_profile, and no exclusions or prerequisites beyond the payment note.

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