Skip to main content
Glama

extract

Read-only

Pull URLs, emails, IPs, dates, numbers, and other items from text or files, deduplicated with counts for quick analysis.

Instructions

Pull items from text, deduped with counts: urls emails ipv4 ipv6 dates times phones money percentages numbers hashtags mentions hex_colors uuids hashes paths ibans versions.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "extract"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxNo
pathNoor a file
sortNo
textNo
kindsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds genuinely useful behavior beyond that: results are deduplicated and returned with counts, which tells the agent about output shape despite there being no output schema. It does not disclose defaults for kinds, sort, or max, nor the response format.

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?

One compact sentence, front-loaded with the action and its output characteristic, then the kind vocabulary. Dense but not padded; the enumeration is long yet each token is informative.

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?

With five parameters, 20% schema coverage, no output schema, and only a readOnly annotation, the description should explain input modes (text vs path), what max and sort do, and what happens when kinds is omitted. None of that is present, so an agent cannot confidently call it without guessing.

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

Parameters2/5

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

Schema description coverage is only 20%, so the description must carry the burden, and it does not. It lists valid kind values but never ties them to the 'kinds' parameter, and leaves max, sort ('first' vs 'count'), and text entirely unexplained, with no stated defaults.

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?

The description gives a specific verb and resource ('Pull items from text') plus the distinctive output behavior ('deduped with counts') and an enumeration of extractable kinds. It is clear what the tool does, though it never contrasts itself with any sibling such as hash or json.

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 or when-not-to-use guidance, and no mention that input can come from a file rather than literal text (that fact only appears in the schema). The agent must infer the use case from the kind list alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.