Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_docs_regex_entity_extractor

Extract emails, URLs, phone numbers, IPs, dates, money, hashtags, and mentions from text to turn unstructured content into structured entity data.

Instructions

[Document Utilities] Extract emails, URLs, phones, IPs, dates, money, hashtags, mentions and more from text Measured p50 10 ms, p95 14 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://docs.caelaralabs.com.

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": "caelara_docs_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 observedv1.0.1

TDQS

B3/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 only contributes latency figures (p50 10 ms, p95 14 ms) plus a docs URL. It never says what happens when 'types' is omitted, whether matching is deterministic, how matches are ordered or returned, or whether results are deduplicated — and with no output schema those gaps are material.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded and the size is reasonable, but the text runs on without a sentence break between the capability list and the benchmark clause, and the 'and more' plus the generic docs link add little. Every element is short but not all of it earns its place.

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 two-parameter extractor with no output schema and no annotations, the description should describe the shape of returned entities and the default behavior of 'types'; neither is covered. Latency and docs reference partially compensate but do not close the gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% but the 'types' schema entry only says 'array of strings' with no enum or valid values; the description enumerates the accepted entity categories in prose, which is meaningful semantics the schema lacks. The trailing 'and more' leaves the list open-ended, which weakens it slightly.

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?

Uses a specific verb ('Extract') with an explicit resource list (emails, URLs, phones, IPs, dates, money, hashtags, mentions), so an agent immediately knows the operation and coverage. It does not differentiate itself from sibling extractors such as caelara_social_caption_hashtag_extractor or caelara_docs_phone_e164_formatter, which keeps it 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this instead of the many sibling extractors, no prerequisites, and no exclusions (e.g., whether to use the dedicated phone formatter when E.164 output is wanted). Usage is only inferable from the verb 'Extract'.

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