Skip to main content
Glama

Text Analysis & Cleanup Tools (Tanod)

text_extract

Read-onlyIdempotent

utilpeek: Extract emails, URLs, domains, IPs, dates and crypto addresses from text. To mask personal data use redact_pii; for names and places use extract_entities. Returns the emails, URLs, domains (ICANN suffixes), IPv4 / IPv6, phone-like numbers, hashtags, mentions, EVM and BTC addresses (Base58Check / Bech32 checksums verified) and dates (normalised to ISO) found in the text, deduplicated and counted in first-seen order; patterns run on RE2 and each hit is re-checked. Phone hits are phone-like digit groups, not validated numbers (see /v1/phone). Typically under 0.7 s. Price: USD 0.001. Free: 10 utilpeek calls per IP per UTC day. The submitted text is never logged or stored.

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 (at most 200,000 characters).
typesNoDefault: all types.
max_per_typeNoMost distinct items returned per type; `truncated` says when more were found.

Output Schema

NameRequiredDescriptionDefault
errorNoOnly on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
notesNo
typesNo
sourceNo
resultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • changedInput schema / properties / max_per_type / description
      Previous value: -"Most distinct items returned per type (1-1000, default 100); `truncated` says when more were found."New value: +"Most distinct items returned per type; `truncated` says when more were found."
    • removedInput schema / properties / max_per_type / title
      Removed value: -"Max Per Type"
    • removedInput schema / properties / text / title
      Removed value: -"Text"
    • removedInput schema / properties / types / default
      Removed value: -null
    • removedInput schema / properties / types / title
      Removed value: -"Types"
    • removedInput schema / title
      Removed value: -"text_extractArguments"
    • removedOutput schema / properties / results / additionalProperties
      Removed value: -{
      -  "properties": {
      -    "items": {
      -      "items": {
      -        "type": [
      -          "object",
      -          "null"
      -        ]
      -      },
      -      "type": [
      -        "array",
      -        "null"
      -      ]
      -    },
      -    "scan_truncated": {
      -      "type": [
      -        "boolean",
      -        "null"
      -      ]
      -    },
      -    "total": {
      -      "type": [
      -        "integer",
      -        "null"
      -      ]
      -    },
      -    "truncated": {
      -      "type": [
      -        "boolean",
      -        "null"
      -      ]
      -    },
      -    "unique": {
      -      "type": [
      -        "integer",
      -        "null"
      -      ]
      -    }
      -  },
      -  "type": [
      -    "object",
      -    "null"
      -  ]
      -}
    • removedOutput schema / properties / types / items
      Removed value: -{
      -  "type": [
      -    "string",
      -    "null"
      -  ]
      -}
  2. Changed2 schema fields changed
    • addedInput schema / properties / max_per_type / description
      Added value: +"Most distinct items returned per type (1-1000, default 100); `truncated` says when more were found."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "error": {
      +      "description": "Only on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object."
      +    },
      +    "notes": {
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "results": {
      +      "additionalProperties": {
      +        "properties": {
      +          "items": {
      +            "items": {
      +              "type": [
      +                "object",
      +                "null"
      +              ]
      +            },
      +            "type": [
      +              "array",
      +              "null"
      +            ]
      +          },
      +          "scan_truncated": {
      +            "type": [
      +              "boolean",
      +              "null"
      +            ]
      +          },
      +          "total": {
      +            "type": [
      +              "integer",
      +              "null"
      +            ]
      +          },
      +          "truncated": {
      +            "type": [
      +              "boolean",
      +              "null"
      +            ]
      +          },
      +          "unique": {
      +            "type": [
      +              "integer",
      +              "null"
      +            ]
      +          }
      +        },
      +        "type": [
      +          "object",
      +          "null"
      +        ]
      +      },
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "source": {
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "types": {
      +      "items": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "type": [
      +        "array",
      +        "null"
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
  3. 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 (readOnly, idempotent, non-destructive, closed-world), the description discloses deduplication and first-seen ordering, RE2 pattern engine with per-hit re-checking, checksum verification for Base58Check/Bech32, ISO normalisation of dates, that phone hits are unvalidated digit groups, typical latency under 0.7s, price, quota, and that submitted text is never logged or stored. These are exactly the traits an agent cannot infer from annotations.

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 routing guidance is front-loaded and every sentence carries operational information. The middle sentence is a long run-on enumeration that partly restates what the output schema already covers, which costs a little efficiency but not clarity.

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 three-parameter extraction tool with a full output schema and rich annotations, the description covers selection guidance, engine behavior, caveats on phone results, latency, cost and privacy. The only redundancy is re-listing return fields the output schema already defines.

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 the schema already documents `text`, `types` and `max_per_type`. The description's enumeration of extractable types loosely maps to the `types` enum but doesn't add format or filtering semantics beyond it, and it never mentions `max_per_type` as an input control. Baseline 3 applies when the schema does the heavy lifting.

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 enumerated set of resources (emails, URLs, domains, IPs, dates, crypto addresses) and explicitly contrasts itself with two named siblings, redact_pii and extract_entities. An agent can distinguish it from extract_links or text_stats without inspecting any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

It gives explicit routing rules: use redact_pii to mask personal data, use extract_entities for names and places. It also states the free-tier constraint (10 calls per IP per UTC day) and price, which shapes when the tool is a sensible choice.

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.