Skip to main content
Glama
openapi-mcp-sdk

openapi-mcp-sdk

check_email_start

check_email_start
Read-onlyIdempotent

Check an email address for SPF/DMARC details, disposability, and fraud indicators to validate sender trust and reduce risk.

Instructions

Retrieves detailed information about an email address (spf, dmark, disposability, frauds) Args: email: the email to check

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": {
      "email": "<email>"
    },
    "name": "check_email_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered. The description adds the returned data categories, which is real value, but omits potentially important behavior such as whether the check is asynchronous (the "start" suffix and the existence of check_async_status suggest it may be) or expected latency.

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, front-loaded lines with no padding; the purpose leads and the argument follows. The inline "Args:" block is slightly informal but costs nothing.

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?

With no output schema, the description carries the burden of explaining return values and does so only as a bare field list, misspelling one of them ("dmark"). Combined with the missing async/sync disclosure and no sibling routing, the definition is adequate but leaves real gaps for an agent deciding how to call and interpret it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single parameter is only restated as "the email to check", which adds no format, validation, or normalization meaning beyond the schema's string type. Nothing tells the agent about accepted domains, casing, or malformed input handling.

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 names a specific verb and resource ("Retrieves detailed information about an email address") and enumerates the data returned (spf, dmarc, disposability, frauds), so an agent knows what it gets. It stops short of differentiating itself from the sibling check_email_advanced, leaving the basic-vs-advanced split unexplained.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no guidance on when to pick this over check_email_advanced, or what "start" implies about scope or timing. The agent must infer usage purely from the tool name.

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