Skip to main content
Glama

Check email syntax

bursia_email_syntax
Read-onlyIdempotent

Check the syntax of an email address (no mailbox lookup, nothing is sent). Pure computation, free.

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

Input Schema

NameRequiredDescriptionDefault
emailYesThe email address to check (syntax only; no message is sent).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / email / description
      Added value: +"The email address to check (syntax only; no message is sent)."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive, and closed-world, so the safety profile is free. The description adds genuinely non-redundant behavior: this is pure local computation, incurs no external dispatch, and is free — exactly the cost/latency signal an agent needs to call it liberally. It stops short of saying whether invalid input raises an error or returns a falsey result.

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?

A single sentence with the scope constraint parenthesized mid-sentence and no filler. Nothing could be removed without losing a distinct fact (no lookup, nothing sent, pure computation, free).

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 one-parameter pure-computation tool this covers purpose, side-effect absence, and cost, which is nearly everything needed. The remaining gap is return shape — there is no output schema, and the description doesn't say whether the result is a boolean, a parsed verdict, or a list of syntax errors.

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?

There is a single parameter with 100% schema description coverage, which already says syntax-only and no message is sent. The description adds nothing about the parameter beyond what the schema states, so the baseline 3 applies. No syntax rules or format expectations are conveyed for the input.

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 and resource ("check the syntax of an email address") and immediately bounds it against the adjacent concept of deliverability validation ("no mailbox lookup, nothing is sent"). That scope note distinguishes it from mailbox-verification services and from sibling validators like bursia_iban_validate. An agent knows exactly what this does without opening the schema.

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?

The description tells the agent what the tool does NOT do (no mailbox lookup, nothing sent), which is partial usage guidance, but it never states when to choose it over alternatives or what a caller should do after a failure. Usage is implied by the name and scope rather than explicitly routed.

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