Skip to main content
Glama

Text keywords

text_keywords
Read-onlyIdempotent

Deterministic keyword, keyphrase, proper-noun, URL, email, hashtag, ticker, EVM-address, and amount extractor (<5 ms, up to 32,000 chars). $0.001 per call over x402 or X-API-Key. Call once without payment for terms, then call again with payment.

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_keywords"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText to extract keywords and entities from.
top_kNoMax keywords to return (1-50, default 15).
paymentNosigned x402 payment payload (PAYMENT-SIGNATURE).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnly, idempotent, openWorld) by disclosing determinism, sub-5 ms latency, a 32,000-character input ceiling, and a concrete price of $0.001 per call. The two-step x402/X-API-Key payment handshake is exactly the kind of behavioral detail an agent cannot infer from structured fields and would otherwise fail on.

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

Conciseness5/5

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

Two tight sentences: capability and entity list first, then cost, limits, and the payment procedure. No filler, and the highest-risk operational detail (call twice for payment) is placed last where it is easy to retain.

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?

With no output schema, the description carries the burden of describing results, and the enumerated entity types largely do that. It stops short of stating the return shape (e.g., scored list vs. grouped entities) or how `top_k` interacts with entity types, which is a modest gap for a tool with 3 parameters.

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 baseline is 3; the description earns an extra point by explaining the runtime meaning of `payment` — that the first call omits it to retrieve terms and the second includes it. `text` and `top_k` add nothing beyond the schema, but the payment semantics are a real addition.

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?

States a specific verb (extract) and resource (keywords plus a concrete list of entity types: proper nouns, URLs, emails, hashtags, tickers, EVM addresses, amounts), so the agent knows exactly what comes back. It does not differentiate itself from sibling text tools such as text_classify or text_summarize, which keeps it from 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 Guidelines3/5

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

Gives clear invocation guidance for the payment flow — call once without `payment` to get terms, then again with `payment` — which is genuinely useful operational context. It offers no guidance on when to choose this over sibling extraction/classification tools or what input text is appropriate, so usage is implied rather than fully scoped.

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