Skip to main content
Glama

secureIT Sicherheits-Checks

Teilnahmezertifikat prüfen

zertifikat_pruefen

Prüft, ob eine Zertifikatsnummer zu einem gültigen secureIT-Zertifikat (Schulung mit Phishing-Training oder Kursbescheinigung) gehört. Gibt nur zurück, was auch die öffentliche Prüfseite zeigt. Für Versicherer, Makler und Auftraggeber.

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": {
      "nummer": "<nummer>"
    },
    "name": "zertifikat_pruefen"
  }
}

Input Schema

NameRequiredDescriptionDefault
nummerYesDie Zertifikatsnummer vom Zertifikat.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It helpfully discloses output scope ('Gibt nur zurück, was auch die öffentliche Prüfseite zeigt'), implying a read-only, non-privileged lookup, but says nothing about authentication needs, rate limits, or error behavior for invalid numbers.

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?

Three short sentences with the core purpose front-loaded; no filler. The audience clause is the only mildly expendable element.

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 read tool with no output schema, the description covers purpose, validity definition, and output scope. Only the absence of guidance on invalid/non-existent certificate handling keeps it from being fully complete.

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?

One parameter at 100% schema description coverage, so the schema already documents 'nummer' fully. The description confirms the identifier is a certificate number but adds no format, length, or validation detail beyond the schema, so a baseline 3 is correct.

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 (prüft) and resource (Zertifikatsnummer / secureIT-Zertifikat) and clarifies what counts as valid (Schulung mit Phishing-Training oder Kursbescheinigung). No sibling tool performs certificate verification, so the agent can distinguish it easily.

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 only implied: the audience clause 'Für Versicherer, Makler und Auftraggeber' hints at who needs it, but there is no explicit when-to-use, when-not, or named alternative among the 16 siblings. Adequate but leaves routing to inference.

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