Skip to main content
Glama

Caelara Labs Document Utilities

regex_entity_extractor

Extract emails, URLs, phones, IPs, dates, money, hashtags, mentions and more from text

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

Input Schema

NameRequiredDescriptionDefault
textYesText to scan
typesNoEntity types to extract (array of strings)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations and no output schema, the description carries the full behavioral burden and delivers very little. It does not say what the result looks like (matches with offsets? deduplicated? ordered?), what happens when the optional types argument is omitted, or whether extraction is case-sensitive or overlapping.

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 sentence with no filler or repetition. It is efficient, though the brevity is partly a symptom of under-specification rather than disciplined editing.

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?

For a tool with no annotations and no output schema, the description should explain at minimum the shape of the returned entities and the default behavior when "types" is omitted. Neither is present, so an agent cannot predict the result format before calling.

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 coverage is 100%, so both parameters are already documented and the baseline is 3. The description adds partial value by enumerating plausible values for the otherwise enum-less "types" array, but the open-ended "and more" leaves that value set ambiguous.

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?

"Extract" plus an enumerated list of entity kinds (emails, URLs, phones, IPs, dates, money, hashtags, mentions) gives a concrete verb and resource scope. The sibling list is dominated by converters/normalizers, so the tool is naturally distinguishable, but the description never states that distinction explicitly.

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 when-to-use guidance, no indication of when a narrower sibling (e.g. address_normalizer or phone_e164_formatter) is preferable, and no prerequisites or input expectations. The agent must infer applicability from the tool name and the entity list alone.

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