Skip to main content
Glama

Extract email addresses from text

extract_emails
Read-only

Extract all email addresses found in a block of free-form text (notes, pasted documents, signatures). Optionally deduplicates and lowercases the results.

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": {
      "text": "<text>"
    },
    "name": "extract_emails"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesFree-form text to scan for email addresses.
lowercaseNoLowercase all extracted addresses. Default true.
deduplicateNoRemove duplicate addresses. Default true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds that deduplication and lowercasing are optional toggles, but that merely restates the schema defaults and says nothing about the shape of the returned results or handling of edge cases like malformed addresses.

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 tight sentences with the core action front-loaded and no filler. The second sentence is slightly redundant with the schema defaults but is short enough to earn its place as a summary of optional behavior.

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 simple three-parameter, read-only extraction tool with full schema coverage and no output schema, the description covers what an agent needs to call it correctly. The only gap is the return shape (a list of strings versus a structured object), which is a minor omission for a single-purpose tool.

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?

Schema description coverage is 100%, so all three parameters are already documented with types and defaults. The description mentions deduplication and lowercasing but contributes no additional semantics such as case-collision behavior or ordering of results, so the baseline of 3 applies.

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 ("extract all email addresses") and scopes the input to "a block of free-form text," with concrete examples (notes, pasted documents, signatures). It does not distinguish itself from plausible siblings like clean_email_list or verify_email, so it falls just short of a 5.

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 use case is implied clearly by the examples of input text, but there is no explicit when-to-use framing and no mention of when to prefer clean_email_list or verify_email instead. An agent can infer the scenario but must reason about alternatives on its own.

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.