secureIT Sicherheits-Checks

Phishing-Selbsttest: Status abfragen

phishing_selbsttest_status

Zeigt, ob die Person den Selbsttest freigegeben hat und wie weit er ist. Die persönliche Auswertung (wer worauf geklickt hat) wird aus Datenschutzgründen NICHT herausgegeben — die bekommt ausschliesslich die getestete Person per E-Mail.

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

Input Schema

Name	Required	Description	Default
`kennung`	Yes	Kennung aus `phishing_selbsttest_anfordern`.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 13, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does disclose a key behavioral constraint: the personal evaluation is deliberately not returned for privacy reasons and only the tested person receives it by email. It does not state read-only behavior explicitly or mention authentication, but the privacy caveat is substantial context.

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 tightly written sentences: the first front-loads the purpose, the second adds a crucial privacy caveat. Every sentence earns its place with no filler.

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?

The tool is simple (one required parameter, no output schema, no annotations). The description explains what information is returned (release status and progress) and what is intentionally withheld, which is complete enough for an agent to call it correctly, though it could specify the return shape more precisely.

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 description coverage is 100%, and the single parameter (Kennung) is fully documented in the schema. The description adds no syntax, format, or validation details beyond what the schema already provides, so the baseline of 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 states a specific verb ('Zeigt') and resource ('Selbsttest'-Status), making clear it reports whether the person released the self-test and how far it has progressed. It distinguishes itself implicitly from the request tool by focusing on status, but does not explicitly name alternatives.

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 implied: query the status of a previously requested self-test using its Kennung. There is no explicit when-to-use guidance, no named alternative, and no statement of prerequisites beyond what the schema parameter description provides.

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?