Skip to main content
Glama

Text Analysis & Cleanup Tools (Tanod)

text_frequency

Read-onlyIdempotent

utilpeek: Count word and n-gram frequencies in a text. For scored keyphrases use text_keywords. Returns the most frequent words or 2-3 word n-grams (n-grams never cross punctuation) with count and share, dropping stop words (en, es, fr, de, pt, it, nl, or none), and optionally character counts. Typically under 0.3 s. Price: USD 0.001. Free: 10 utilpeek calls per IP per UTC day. The submitted text is never logged or stored. Docs: https://tanod.dev/learn/keyword-extraction-api.html

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

Input Schema

NameRequiredDescriptionDefault
textYesThe text (at most 200,000 characters).
ngramNoTerm length in words: 1 (default), 2 or 3; n-grams never span punctuation.
top_nNoMost frequent terms to return.
languageNoStop-word list to drop (none = keep every word).en
charactersNoAlso count characters (whitespace excluded).
min_lengthNoShortest word counted, in characters (1-50, default 1; single words only, ngram=1).
case_sensitiveNoCount "Word" and "word" apart (default false: terms are lowercased).
include_numbersNoAlso count numeric tokens such as 2026.
remove_stopwordsNoDrop the stop words of `language`.

Output Schema

NameRequiredDescriptionDefault
topNo
errorNoOnly on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
ngramNo
totalNo
sourceNo
uniqueNo
languageNo
charactersNo
stopwords_removedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changed
    • removedInput schema / properties / case_sensitive / title
      Removed value: -"Case Sensitive"
    • removedInput schema / properties / characters / title
      Removed value: -"Characters"
    • changedInput schema / properties / include_numbers / description
      Previous value: -"Also count numeric tokens such as 2026 (default false)."New value: +"Also count numeric tokens such as 2026."
    • removedInput schema / properties / include_numbers / title
      Removed value: -"Include Numbers"
    • removedInput schema / properties / language / title
      Removed value: -"Language"
    • removedInput schema / properties / min_length / title
      Removed value: -"Min Length"
    • removedInput schema / properties / ngram / title
      Removed value: -"Ngram"
    • changedInput schema / properties / remove_stopwords / description
      Previous value: -"Drop the stop words of `language` (default true)."New value: +"Drop the stop words of `language`."
    • removedInput schema / properties / remove_stopwords / title
      Removed value: -"Remove Stopwords"
    • removedInput schema / properties / text / title
      Removed value: -"Text"
    • changedInput schema / properties / top_n / description
      Previous value: -"Most frequent terms to return (1-1000, default 50)."New value: +"Most frequent terms to return."
    • removedInput schema / properties / top_n / title
      Removed value: -"Top N"
    • removedInput schema / title
      Removed value: -"text_frequencyArguments"
    • removedOutput schema / properties / top / items
      Removed value: -{
      -  "type": [
      -    "object",
      -    "null"
      -  ]
      -}
  2. Changed7 schema fields changed
    • addedInput schema / properties / case_sensitive / description
      Added value: +"Count \"Word\" and \"word\" apart (default false: terms are lowercased)."
    • addedInput schema / properties / include_numbers / description
      Added value: +"Also count numeric tokens such as 2026 (default false)."
    • addedInput schema / properties / min_length / description
      Added value: +"Shortest word counted, in characters (1-50, default 1; single words only, ngram=1)."
    • addedInput schema / properties / ngram / description
      Added value: +"Term length in words: 1 (default), 2 or 3; n-grams never span punctuation."
    • addedInput schema / properties / remove_stopwords / description
      Added value: +"Drop the stop words of `language` (default true)."
    • addedInput schema / properties / top_n / description
      Added value: +"Most frequent terms to return (1-1000, default 50)."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "characters": {
      +      "type": [
      +        "array",
      +        "null"
      +      ]
      +    },
      +    "error": {
      +      "description": "Only on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object."
      +    },
      +    "language": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "ngram": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "source": {
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "stopwords_removed": {
      +      "type": [
      +        "boolean",
      +        "null"
      +      ]
      +    },
      +    "top": {
      +      "items": {
      +        "type": [
      +          "object",
      +          "null"
      +        ]
      +      },
      +      "type": [
      +        "array",
      +        "null"
      +      ]
      +    },
      +    "total": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "unique": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, and the description adds substantial context beyond that: n-grams never cross punctuation, stop-word lists per language, typical latency under 0.3 s, price, free-tier quota, and a no-logging/no-storage guarantee. This is exactly the kind of behavioral detail annotations cannot express.

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 purpose and the sibling alternative, then behavior, then operational metadata. Dense and mostly waste-free, though the pricing/free-tier/docs sentence is boilerplate that dilutes the core description slightly.

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?

With an output schema present, return values need not be explained, and the description covers purpose, alternative, stop-word behavior, n-gram constraints, and operational limits. Nothing an agent needs to invoke this correctly is missing.

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 every parameter is already documented in the schema. The description restates a few semantics (stop-word languages, n-gram punctuation rule, optional character counts) but adds no syntax or format detail beyond what the schema provides, so the baseline 3 applies.

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 ('Count word and n-gram frequencies in a text') and immediately distinguishes itself from the sibling text_keywords by naming the scored-keyphrase alternative. An agent can tell what this does and what it does not do 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?

Explicitly routes the agent to text_keywords when scored keyphrases are wanted, which is the main ambiguity among siblings. It does not address other potentially overlapping siblings such as text_stats, but the primary when-to-use condition is clear.

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.