Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Extract emails, URLs and more: find email addresses, URLs, phone numbers and other items in a text

text_extract
Read-only

Find all email addresses, URLs, phone-number-like strings, hashtags, @mentions and numbers in a text, each list de-duplicated. Use to pull contacts and links out of scraped pages or messages. Example: text=Mail ada@example.com or see https://example.com #news @ada +46 70 123 45 67. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not 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": {
      "text": "<text>"
    },
    "name": "text_extract"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe text

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations the description discloses genuinely new operational facts: per-call billing via x402 USDC or card key, the first 25 calls free, failed calls free, and that repeats are not free. The last point explicitly reinforces the non-idempotent hint, and "reads or computes only and changes nothing" is consistent with readOnlyHint=true and destructiveHint=false.

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?

The purpose is front-loaded, then usage, an example, pricing and a safety note, with no filler. The pricing sentence is longer than the rest and is the least relevant to tool selection, which keeps this just short of a 5.

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 tool with no output schema, the description covers purpose, selection context, dedup semantics of the returned lists, cost model and side-effect profile. The precise shape of the response (how the per-type lists are keyed) is not stated, but that gap is small given the tool's simplicity.

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%, so the single 'text' parameter is already documented and the baseline is 3. The description adds modest value by illustrating the sort of payload the parameter is expected to contain, showing emails, URLs, hashtags, mentions and a phone number bundled in one string.

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?

The description opens with a specific verb and an explicit enumeration of the resources extracted: emails, URLs, phone-number-like strings, hashtags, @mentions and numbers, plus de-duplication. That scope is broad enough to distinguish it from narrower siblings such as phone_validate, which handles one entity type, without the agent needing to open 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 Guidelines4/5

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

"Use to pull contacts and links out of scraped pages or messages" gives a clear triggering context, and the worked example makes the expected input concrete. There are no explicit exclusions or named alternatives, so the agent must infer that phone_validate is the choice for validation rather than extraction.

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.