secureIT Sicherheits-Checks

Zustellbarkeits-Check abfragen

mailcheck_ergebnis

Liefert die Auswertung einer zuvor gestarteten Prüfung: SPF, DKIM, DMARC, TLS und Reverse-DNS der tatsächlich gesendeten Mail. Status "wartet" bedeutet, dass noch keine Mail eingegangen ist — dann nach einigen Sekunden erneut abfragen.

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": {
      "kennung": "<kennung>"
    },
    "name": "mailcheck_ergebnis"
  }
}

Input Schema

Name	Required	Description	Default
`kennung`	Yes	Die von `mailcheck_start` zurückgegebene Kennung.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 13, 2026

TDQS

A4.2/5.0

Behavior4/5

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

No annotations, so the description carries the full burden. It discloses the return content areas and, importantly, the asynchronous waiting-state semantics with retry guidance — genuinely useful behavior beyond the schema. It does not cover error cases (invalid/expired kennung) or result lifetime.

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 sentences, zero filler, with the core purpose first and the polling caveat second. Every clause earns its place.

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 single-parameter polling tool with no output schema, the description covers the essentials: what is evaluated and how to handle the pending state. Minor gaps remain around failure modes and how long the kennung stays valid.

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?

Only one parameter with 100% schema description coverage; the schema already explains that kennung comes from mailcheck_start. The description adds no additional syntax, format, or validity constraints beyond the schema, so the baseline of 3 applies.

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 specific verb+resource ('Liefert die Auswertung einer zuvor gestarteten Prüfung') and enumerates exactly what is evaluated (SPF, DKIM, DMARC, TLS, Reverse-DNS). This clearly separates it from mailcheck_start (which launches the check) and mail_pruefen.

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?

Explicitly defines the polling condition: status 'wartet' means no mail has arrived yet and the agent should re-query after a few seconds. It also frames the tool as operating on a previously started check, implying use after mailcheck_start. No explicit naming of alternatives or when-not-to-use, so not a 5.

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

All secureIT Sicherheits-Checks 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?