Skip to main content
Glama

Word frequency

gj_words
Read-onlyIdempotent

Counts word usage across a poet's or book's poems, listing the most frequent words or checking how often one specific word appears.

Instructions

Count word use in a poet's or book's poems: the most frequent words, or how often one word appears.

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

Input Schema

NameRequiredDescriptionDefault
wordNoCount this exact word instead of listing top words.
limitNoTop words to list.
cat_idNoBook/category id (a poet's whole divan: its root cat_id).
poet_idNoPoet id (all their books together).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered and the description need only add operational context. It adds scope (a poet's whole corpus or a book's poems) which is useful beyond the schema, but says nothing about what happens with no scope argument, how counts are produced, or what the response looks like. With annotations doing the safety work, this is adequate rather than rich.

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?

A single sentence with the counting action front-loaded and the two modes spelled out after the colon. There is no filler, no restatement of the title, and nothing that could be cut without losing information.

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

Completeness3/5

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

This is a simple read-only tool with full schema coverage and no output schema, so the bar is modest and the two operating modes are covered. What is missing is the default behavior when neither poet_id nor cat_id is supplied (whole corpus? error?) and any hint that results are word/count pairs, which matters since no output schema exists to explain the return shape.

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 the schema already explains word, limit, cat_id and poet_id individually; the baseline of 3 applies. The description does add meaning the schema cannot, namely that supplying a word switches the tool from ranking to single-word counting, but it never mentions the limit cap or the root cat_id versus poet_id distinction that the schema itself flags.

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 concrete verb and resource ('Count word use in a poet's or book's poems') and splits it into two recognizable modes: top-N frequency listing versus lookup of one word's count. That is clear enough to act on without opening the schema, but nothing in the wording separates it from siblings such as gj_search or gj_literary, which an agent could plausibly reach for instead.

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?

The two modes ('the most frequent words, or how often one word appears') imply which mode fits which question, but the choice between them is left to the reader rather than stated as a condition. There is no guidance on when to prefer this over text-search or literary-analysis siblings, and no note on whether poet_id and cat_id can be combined or which wins.

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