Skip to main content
Glama

DNSFix

Get DMARC summary

get_dmarc_summary
Read-onlyIdempotent

Who sent email as your domain (from DMARC reports) and how much passed SPF or DKIM. Needs a connected DNSFix™ account with domain watching.

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

Input Schema

NameRequiredDescriptionDefault
daysNoOptional: how many days of reports to sum up, 1 to 90 (default 30)
domainYesA domain name, for example yourbusiness.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / days / description
      Added value: +"Optional: how many days of reports to sum up, 1 to 90 (default 30)"
  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 declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds meaningful context beyond that: the data originates from DMARC aggregate reports (so results lag and depend on report volume) and it requires a connected account actively watching the domain. It does not state what happens when no reports exist, but the added precondition is substantive.

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 short sentences, both earning their place, with the capability statement front-loaded ahead of the prerequisite. The opening clause 'Who sent email as your domain' is slightly awkward to parse but conveys a lot in few words.

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 two-parameter read tool with no output schema, the description conveys what the response covers (senders and pass rates) and the account prerequisite, and the schema fully documents days and domain. The only gap is the absence of any note about report lag or behavior when no reports are available.

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%: the domain parameter has an example and days is documented as 1–90 with a default of 30. The description adds no format, timezone, or aggregation detail for either parameter, so the baseline 3 applies.

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 resource (DMARC reports) and the specific output content — senders using the domain plus SPF/DKIM pass volume — which is far more informative than the name alone. It does not explicitly distinguish itself from check_dmarc or build_dmarc_record, but 'from DMARC reports' and 'how much passed' clearly mark it as an aggregate-report reader rather than a record validator or builder.

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?

Use is implied by 'from DMARC reports' versus the sibling check_dmarc, and a precondition (connected account with domain watching) is stated. However, there is no explicit when-to-use/when-not guidance, and the agent must infer that this tool requires an existing reporting stream rather than live DNS checks.

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