Skip to main content
Glama

Once-used vocabulary

bpj_hapax_vocabulary
Read-onlyIdempotent

List words used exactly once and calculate their share of total tokens.

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and repeatability are covered structurally. The description adds the useful fact that a derived ratio is computed alongside the word list, but it never states tokenization rules, case sensitivity, or how punctuation/non-word characters affect 'exactly once' counts.

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 tight sentence with the primary action front-loaded and the secondary calculation attached; nothing is redundant or padded.

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?

For a one-parameter, non-destructive text-analysis tool with no output schema, the description covers the core behavior. It still leaves the return shape (word list plus numeric share, ordering, rounding) and text-normalization behavior to inference, which matters for interpreting 'used exactly once'.

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?

There is one parameter with 0% schema description coverage; the only in-schema hint is the title 'Source text' and a 6000-character cap. The description's phrase 'share of total tokens' clarifies the denominator used for the ratio, which is real added meaning, but it does not say what units the input is split into or whether the cap affects results.

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?

The description names a specific verb ('List') and a precisely defined resource ('words used exactly once'), plus a secondary computation ('their share of total tokens'). That is far more specific than the title alone, though it never distinguishes itself from near-neighbors such as bpj_adjacent_word_echo.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no named alternative. The only implicit signal is that the tool consumes a source text, which an agent could infer from the schema anyway.

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.