Skip to main content
Glama

Extract keywords and keyphrases from a text

text_keywords
Read-only

Keywords and keyphrases from a text by RAKE (Rose et al., 2010) in pure code: phrases between stopwords and punctuation, scored by word degree and frequency, with counts. Stopword lists for en, de, fr, es, it, pt, nl and tr. Body { text, language, limit }: up to 100 KB, limit 1 to 50. Related tools on this server, for a different need: text_answer when you need answers a question from the given text only; text_chunk when you need to generate overlapping text chunks with character offsets. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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
textYesThe text, up to 100 KB (JSON body field)
limitNoKeywords to return, 1 to 50, default 10
languageNoen (default), de, fr, es, it, pt, nl or tr

Output Schema

NameRequiredDescriptionDefault
countNo
sourceNo
keywordsNo
languageNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the read-only, open-world profile, and the description adds genuinely new behavioral facts beyond them: supported stopword languages, the 100 KB input ceiling, the 1-50 result cap, and a per-call price with explicit statement that 'failed calls are not charged.' Cost and failure-charging behavior are exactly the kind of context annotations never carry.

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?

Front-loaded with the purpose and algorithm, then constraints, then alternatives, then price — a sensible order for an agent skimming. It is a dense single paragraph and the algorithm internals ('word degree and frequency') are arguably more than an agent needs to choose the tool, but nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the description does not need to explain return values, and it still notes results include counts. Input limits, language coverage, algorithm basis, sibling routing, and pricing are all present, leaving nothing an agent needs in order to call it correctly.

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 coverage is 100%, so the baseline is 3; the description's 'Body { text, language, limit }: up to 100 KB, limit 1 to 50' largely restates what the schema already declares. The only marginal addition is framing the output as 'with counts,' which is not a parameter but sets expectations for what limit controls.

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 specific verb and resource ('Keywords and keyphrases from a text') and names the exact algorithm (RAKE, Rose et al. 2010) with the mechanism ('phrases between stopwords and punctuation, scored by word degree and frequency'). That mechanism level of detail clearly separates it from sibling tools like text_answer and text_chunk.

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?

Explicitly routes the agent to alternatives with the selecting condition: text_answer 'when you need answers a question from the given text only' and text_chunk 'when you need to generate overlapping text chunks with character offsets.' Combined with the stated input caps (100 KB, limit 1-50), the agent knows both when this tool fits and when another does.

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