Skip to main content
Glama

AutoPay

security_scan_dns

DNS / e-mail security check (passive only): SPF, DMARC, DKIM (common selectors), MX, CAA, DNSSEC; score + grade. $0.003; synchronous, charged only on success. Pay with X-PAYMENT (x402 USDC on Base) or a prepaid API key.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "security_scan_dns"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoSite URL, e.g. https://example.com
domainNoAlternative to url: bare domain, e.g. example.com

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, the description carries the full burden and does real work: passive-only semantics, synchronous execution, a concrete price ($0.003), charge-on-success billing, and the two accepted payment paths (X-PAYMENT x402 USDC or prepaid API key). Remaining gaps are rate limits and whether DKIM coverage depends on selector guessing, but the cost and safely-side-effect profile an agent needs before calling are disclosed.

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?

Roughly three clauses, each front-loaded and purposeful: what it checks, how it is priced/executed, how to pay. No filler, though the closing payment clause is dense enough to be skimmed.

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?

Because there is no output schema, the 'score + grade' phrase is necessary and correctly included. Against a zero-required-parameter tool with two mutually alternative inputs, the description should say that url or domain (one of them) must be supplied; that operating requirement is left unstated.

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 url and domain parameters are already self-documenting with examples, making 3 the correct baseline. The description adds no meaning about the url-versus-domain alternative or that exactly one is effectively needed, so it does not exceed the schema.

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 names a specific verb+resource ('DNS / e-mail security check') and enumerates exactly what is inspected (SPF, DMARC, DKIM common selectors, MX, CAA, DNSSEC) plus its return shape (score + grade). That enumeration lets an agent distinguish it from security_scan_headers or security_scan_tls without opening the schema.

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?

'passive only' usefully signals this is a non-intrusive lookup, which implies when to pick it over an active scan. However, it never explicitly states when to choose this versus security_scan_tls, security_scan_headers, security_scan_full, or the umbrella security_scan, leaving the routing decision to inference.

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