Skip to main content
Glama

Moving lexical diversity

bpj_lexical_diversity_mattr
Read-onlyIdempotent

Compute mean type-token ratio across sliding windows of up to 50 words.

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

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, non-destructive and closed-world, so the safety profile is covered. The description adds the key behavioral fact that averaging happens over sliding windows of up to 50 words, but says nothing about how text is tokenized (case, punctuation), what happens with short input, or whether the window size is configurable.

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 front-loaded sentence with no filler; the core operation and the windowing detail are both stated immediately.

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, no-output-schema computation tool this is close to adequate, but it leaves the agent guessing about the return value's form (a single ratio, presumably 0–1), tokenization rules, and behavior on texts shorter than the window.

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?

Only one parameter ('text') exists and schema description coverage is 0%, but the parameter is self-evident and constrained by maxLength 6000. The description's 'up to 50 words' window implicitly tells the agent the input should be prose with enough words, which is mild added meaning beyond the schema.

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 ('compute') and a specific metric ('mean type-token ratio across sliding windows'), so the operation is unambiguous. It does not distinguish itself from siblings, but the listed siblings are unrelated series/encoding utilities, so differentiation matters less here.

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 guidance on when to choose this moving-window diversity measure over any alternative, and no stated preconditions. It also omits the practical caveat that texts shorter than the window size produce degenerate or meaningless values.

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.