Skip to main content
Glama

entity-extract

Entity extract. Any text in, URL-encoded as the text query parameter (up to 12,000 bytes), an extraction out: eight families (emails, URLs, ISO dates, US dates, money, percentages, organizations, cashtag tickers), every match with its occurrence count and first line, the full pattern set published verbatim in the result. Price: $0.10 per call, paid in USDC on Base mainnet over x402; an unpaid call answers HTTP 402 with the exact machine-readable payment terms.

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": "entity-extract"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe text to scan for entities (up to 12,000 bytes).

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?

With no annotations, the description carries the full burden and does so: it discloses pricing ($0.10 per call), the payment rail (USDC on Base mainnet over x402), and the exact failure mode (unpaid call returns HTTP 402 with machine-readable terms). It also describes the result shape — occurrence count, first line, and the pattern set published verbatim — which is behavior no annotation could supply.

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?

Dense and front-loaded: purpose first, then input constraint, output shape, and cost/error behavior. The telegraphic 'text in ... extraction out' phrasing is slightly compressed for readability, but no sentence is filler.

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 and no annotations, the description covers input limits, output structure, price, and payment-failure behavior — everything needed to call it correctly. Minor residual ambiguity exists around how strictly URL encoding is enforced and what happens on oversized input, but nothing essential is missing.

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% for the single parameter, so baseline is 3; the description adds real value by stating the text must be URL-encoded when passed as the query parameter, which the schema does not say. The byte limit is repeated from the schema, but the encoding requirement is net-new guidance.

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?

States a concrete verb and resource ('Entity extract. Any text in ... an extraction out') and enumerates exactly what is produced: eight families (emails, URLs, ISO dates, US dates, money, percentages, organizations, cashtag tickers). An agent knows precisely what goes in and what comes out without opening 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?

Gives clear applicability ('any text in') plus a hard constraint of up to 12,000 bytes, and discloses the cost barrier ($0.10/call). It stops short of explicit when-not-to-use guidance or naming an alternative tool, but the input condition is unambiguous.

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