Skip to main content
Glama

Explain issue

explain_issue
Read-onlyIdempotent

Ask the IntoDNS.ai AI service for a plain-language explanation of one specific issue (e.g. spf_missing, no_dnssec). Returns severity, business impact, root cause, and recommended fix steps as structured text.

Instructions

Ask the IntoDNS.ai AI service for a plain-language explanation of one specific issue (e.g. spf_missing, no_dnssec). Returns severity, business impact, root cause, and recommended fix steps as structured text. Read-only POST to /ai/explain — never mutates DNS or domain state. Provide domain and issue (enum); pass context from prior scan output (e.g. scan_domain result) for higher-quality answers. Use after scan_domain when an agent needs to walk a user through why a finding matters; use generate_dns_fix for the actual DNS record snippet that resolves 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>",
      "issue": "<issue>"
    },
    "name": "explain_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
issueYesIssue identifier, e.g. spf_missing or no_dnssec
domainYesDomain name only, e.g. example.com (no URL, path, or port)
contextNoOptional issue context from scan output

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.11.1
    • addedInput schema / properties / issue / description
      Added value: +"Issue identifier, e.g. spf_missing or no_dnssec"
  2. Changed5 schema fields changedv1.10.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / context / propertyNames
      Added value: +{
      +  "type": "string"
      +}
    • changedInput schema / properties / domain / description
      Previous value: -"Domain name, e.g. example.com"New value: +"Domain name only, e.g. example.com (no URL, path, or port)"
    • addedInput schema / properties / domain / maxLength
      Added value: +253
    • changedInput schema / properties / issue / enum
      Previous value: -[
      -  "no_ipv6",
      -  "no_dnssec",
      -  "spf_missing",
      -  "spf_too_many_lookups",
      -  "spf_softfail",
      -  "dkim_missing",
      -  "dmarc_missing",
      -  "dmarc_none",
      -  "dmarc_quarantine",
      -  "no_caa",
      -  "dane_missing"
      -]New value: +[
      +  "no_a_record",
      +  "no_mx_record",
      +  "mx_ptr_missing",
      +  "mx_fcrdns_missing",
      +  "single_ns",
      +  "dnssec_invalid",
      +  "nsec3_not_compliant",
      +  "rrsig_expiring",
      +  "ds_digest_weak",
      +  "dnskey_algo_weak",
      +  "rrsig_ttl_unsafe",
      +  "chain_incomplete",
      +  "no_ipv6",
      +  "no_ipv6_mail",
      +  "no_dnssec",
      +  "no_spf",
      +  "no_dmarc",
      +  "weak_dmarc",
      +  "no_dkim",
      +  "excessive_verification_records",
      +  "no_http3",
      +  "spf_missing",
      +  "spf_too_many_lookups",
      +  "spf_softfail",
      +  "dkim_missing",
      +  "dmarc_missing",
      +  "dmarc_none",
      +  "dmarc_quarantine",
      +  "no_caa",
      +  "dane_missing"
      +]
  3. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds the concrete endpoint ('POST to /ai/explain') and the reassertion that it 'never mutates DNS or domain state', which resolves the POST-looks-like-a-write ambiguity. It also describes the shape of the returned structured text, which annotations cannot convey.

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?

Front-loads what the tool does, then returns, then safety, then parameter advice, then sibling routing. Four sentences, each carrying distinct information with no restatement of the name or schema.

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?

No output schema exists, so the description's enumeration of return fields (severity, business impact, root cause, fix steps) fills that gap. Prerequisites (a prior scan's context), safety profile, and sibling routing are all covered for a 3-parameter tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the enum and domain format are already documented; the description still adds real value by saying to pass `context` from prior scan output (e.g. scan_domain result) to get 'higher-quality answers', which explains why the optional object parameter exists rather than just what it is.

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?

States a concrete verb and resource ('Ask the IntoDNS.ai AI service for a plain-language explanation of one specific issue'), names example issue identifiers, and enumerates what comes back (severity, business impact, root cause, fix steps). An agent can separate it from generate_dns_fix purely from the text.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit sequencing rule ('Use after scan_domain when an agent needs to walk a user through *why* a finding matters') and names the alternative with its selecting condition ('use generate_dns_fix for the actual DNS record snippet'). No inference required.

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