Skip to main content
Glama
openapi-mcp-sdk

openapi-mcp-sdk

Certified email address availability check

check_pec
Read-only

Verifies whether a specific PEC (Certified Email) address is available, helping users confirm if it can be used.

Instructions

Checks if a specific PEC (Certified Email) address is available.

Use this tool when the user asks if a PEC address is available.

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": {
      "pec": "<pec>"
    },
    "name": "check_pec"
  }
}

Input Schema

NameRequiredDescriptionDefault
pecYesthe pec address to check

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and idempotentHint=false, so the safety profile is covered structurally. The description adds nothing beyond that: it never explains what 'available' means (unregistered? deliverable? reserved?), whether the check is free or consumes credit, or what the reply looks like. For a lookup whose whole value is the binary verdict, that leaves the behavioral picture thin.

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?

Two short sentences, front-loaded with the action and free of filler. The second sentence partially echoes the first ('available' appears in both), which is minor redundancy but not damaging.

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?

This is a simple one-parameter lookup with annotations present, so it does not need much. However, with no output schema, the agent has no way to know whether the response is a bare boolean, a status object, or an error-code list, and the description does not fill that gap. Adequate but with a clear hole around return semantics.

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 required parameter with 100% schema description coverage, so the baseline is a 3 by rule. The description only restates 'a PEC address' and adds no syntax, format, or validation detail (domain expectations, uppercase handling) beyond what the schema already says.

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: 'Checks if a specific PEC (Certified Email) address is available.' The domain-specific term PEC combined with 'availability check' makes the intent unambiguous. It does not, however, distinguish itself from the cluster of sibling check_* email tools (check_email_advanced, check_email_start), leaving the agent to infer the difference from names alone.

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?

'Use this tool when the user asks if a PEC address is available' gives an explicit trigger condition, which is more than nothing. But it is essentially a restatement of the purpose sentence, and it offers no when-not guidance, no mention of the non-PEC email alternatives, and no prerequisites (e.g., that this only applies to Italian certified email).

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