Skip to main content
Glama

Lookproof DNS, mail and TLS security checks

DMARC record parser

dmarc_parse
Read-onlyIdempotent

Use when the user pastes a DMARC record to explain or check before publishing. Returns p, sp, np, adkim, aspf, rua, ruf and unknown tags, with the same findings as dmarc. No DNS lookups. Ex: 'Explain v=DMARC1; p=none'. Free trial without an API key: a few calls a day.

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": {
      "record": "<record>"
    },
    "name": "dmarc_parse"
  }
}

Input Schema

NameRequiredDescriptionDefault
recordYesThe DMARC record as text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive behavior. The description adds useful context beyond them: no DNS lookups, returned fields including unknown tags, same findings as dmarc, and free-trial/rate-limit information. Error handling is not covered, but that is a minor gap for a simple parser.

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?

The description is front-loaded with the trigger and return fields, followed by concise caveats. The phrase 'same findings as dmarc' is slightly ambiguous, and the free-trial note is ancillary, but the overall text has little waste.

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 simple one-parameter parser with rich annotations and no output schema, the description supplies the trigger, output field names, no-DNS behavior, an example, and rate context. Only edge-case or error behavior is missing, which is minor here.

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?

There is one parameter and schema coverage is 100%, so the schema already defines the record string. The description adds an example DMARC record and pasted-text context, but does not add format constraints or parsing rules beyond what the schema provides.

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 states the resource (DMARC record), the action (explain/check a pasted record), and what it returns. It distinguishes from the sibling dmarc tool by taking a pasted record and performing no DNS lookups, so an agent can select it 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 Guidelines4/5

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

It gives an explicit trigger: use when the user pastes a DMARC record to explain or check before publishing. It implies the alternative (dmarc) by saying the findings are the same and that no DNS lookups occur, but does not explicitly state when to choose dmarc instead.

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.