DMARC Shark — Email DNS Checker

Read a saved domain check

get_saved_result

Read-onlyIdempotent

Reads the last saved, timestamped public snapshot without making any DNS queries. Results expire after 90 days.

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_saved_result"
  }
}

Input Schema

Name	Required	Description	Default
`domain`	Yes

Output Schema

Name	Required	Description	Default
`saved`	Yes
`dnssec`	No
`domain`	Yes
`source`	Yes
`findings`	Yes
`checked_at`	Yes
`recommendations`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 5, 2026
- addedOutput schema / properties / dnssec
```
Added value: +{
+  "type": "object"
+}
```
First observedOct 19, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds real value beyond them: no DNS queries are issued and results expire after 90 days. It does not say what happens when no saved snapshot exists or the snapshot has expired.

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 short sentences, zero filler, with the cached-read constraint front-loaded before the expiry caveat. Every clause earns its place.

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?

An output schema exists, so return values need not be explained. However, for a lookup that can plausibly fail on missing or expired snapshots, the description omits the failure behavior and does not clarify the domain argument, leaving gaps for a simple one-parameter tool.

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 single parameter has zero schema description coverage, and the description never explains the domain argument (expected format, whether subdomains are allowed, whether it must match a previously checked domain). The parameter name is self-evident, but the description does not compensate for the coverage gap.

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?

States a specific verb and resource: 'Reads the last saved, timestamped public snapshot.' The phrase 'without making any DNS queries' implicitly distinguishes it from the live-check sibling, though it never names check_domain directly.

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?

Usage is hinted at through the negative constraint (no DNS queries), which suggests using this instead of a live lookup, but there is no explicit when-to-use statement or named alternative. An agent must infer that check_domain is the live counterpart.

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

All DMARC Shark — Email DNS Checker tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?