Skip to main content
Glama
Test MCP Server

Test MCP Server

validate_email

Verifies an email address has a valid format to catch input errors before submission or storage.

Instructions

Validate an email address format

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

Input Schema

NameRequiredDescriptionDefault
emailYesEmail address to validate

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost nothing. It does not say what "valid" means (syntactic regex vs. RFC 5322 vs. DNS/MX reachability), whether the check is purely offline, or what the caller receives back. For a validation tool where the definition of validity is the entire contract, this is a substantive gap.

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?

A single front-loaded phrase with zero filler; the verb and resource lead. It is arguably too terse given the undefined return semantics, but there is no wasted wording to trim.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description is responsible for telling the agent what a validation call yields (boolean, error message, parsed parts) and it does not. Combined with the absent annotations and the undefined strictness of "format," the definition leaves a caller unable to predict the result of the call.

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?

The single parameter is fully documented in the schema (100% coverage, format: email, with its own description), so the schema already does the work. The description adds no constraints, normalization behavior, or edge-case notes beyond that schema entry, which is the expected baseline when coverage is complete.

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 ("Validate") and resource ("an email address format"), so the agent knows exactly what operation it performs. It does not differentiate from siblings, but the listed siblings (add_numbers, echo, get_system_info) are unrelated utilities, so no differentiation is needed.

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 explicit when-to-use guidance, no preconditions, and no note about when a different tool would be preferred. The agent can infer this is a format check, but nothing in the text confirms that inference or excludes alternatives.

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

Deploy Server

Other Tools