Skip to main content
Glama

Word frequency

word_frequency
Read-onlyIdempotent

Finds frequently used words in an essay to reveal overused or repeated terms, returning each word's count and share of total words.

Instructions

Find the words an essay uses most, to spot overused or repeated terms. Inputs: text, and optional top (how many words to list, default 10), min_count (fewest uses for a word to be listed, default 2) and include_common_words (also count small words such as the, and, of and to, default false). Case is ignored, and words under 3 letters are skipped unless include_common_words is true. Each word comes with its count and its share of all the words in the text. Example: "Which words do I overuse in this essay?"

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": "word_frequency"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNoHow many words to list. Default 10.
textYes
min_countNoFewest uses for a word to be listed. Default 2.
include_common_wordsNoAlso count small common words. Default false.

Output Schema

NameRequiredDescriptionDefault
topYes
wordsYes
min_countYes
total_wordsYes
unique_wordsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/closed-world, and the description adds real behavior: case is ignored, words under 3 letters are skipped unless include_common_words is true, and defaults for min_count and top. It doesn't discuss performance or text-size limits, but the added filtering semantics are substantive.

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, then inputs, then rules; every clause carries information, though the trailing example question is mildly redundant with the opening sentence.

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?

Output schema exists so return values needn't be explained, annotations cover the safety profile, and the description still documents output shape (count plus share) and all filtering rules — nothing an agent needs is missing.

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

Parameters5/5

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

Each parameter is explained with its default and meaning, and crucially the interaction between include_common_words and the 3-letter skip rule is spelled out — meaning the description adds beyond the 75%-covered schema.

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 ("Find the words an essay uses most") plus the underlying goal (spot overused/repeated terms), which distinguishes it from siblings like count_text and check_word_limit.

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?

The purpose statement and closing example question ("Which words do I overuse in this essay?") make the use case clear, but it never names an alternative sibling or states when not to use it (e.g., versus count_text).

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