Skip to main content
Glama
Sign In
Lead Cleanup MCP Lite

Lead Cleanup MCP Lite

by digitalsolutionsmagic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

validate_email

Validates email address formatting without network lookup so malformed addresses can be identified before lead list cleanup and de-duplication.

Instructions

Check whether an email address has a valid format (no network lookup).

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
emailYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It usefully discloses that no network lookup occurs, implying a fast, side-effect-free local check, but it never states whether the result is a boolean, an error reason, or what happens with malformed input.

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 front-loaded sentence with zero filler. The key constraint, no network lookup, is included inline where it is most useful.

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?

For a trivial one-parameter tool with no output schema, the description covers the input and the execution scope but omits the shape of the result, which is the entire point of a validation tool. An agent can guess a boolean, but it should not have to.

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 one parameter with 0% schema description coverage, so the description must compensate. It only implies that the input is the email address to validate, adding minimal meaning beyond the property name 'email'.

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 states a specific verb and resource: check an email address for valid format. It is unambiguous about what the tool does, though it never mentions the sibling clean_leads or how the two differ in scope.

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 parenthetical '(no network lookup)' implicitly scopes usage to syntactic-only checks and signals this is not a deliverability or MX verification tool, which is useful. However, there is no explicit statement of when to use this versus clean_leads or any other alternative.

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