Skip to main content
Glama

Repeated three-word phrases

bpj_repeated_word_trigrams
Read-onlyIdempotent

Find repeated three-word sequences with overlapping windows.

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

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 readOnly, idempotent, closed-world, non-destructive behavior, so safety is fully covered elsewhere. The one genuinely additive detail is 'overlapping windows', which hints that subsequences slide by one word rather than being disjoint chunks — but case sensitivity, punctuation handling, and whether results carry counts are not addressed.

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?

One short clause with zero filler; the detecting behavior and the windowing qualifier are front-loaded. It is efficient but borders on terse, offering no framing sentence to orient the agent before the qualifier.

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?

The tool is simple (one string input, no nesting, no output schema), yet with no output schema the description should say what comes back — a list of repeated trigrams, with occurrence counts or positions? It also omits any note about the 6000-character limit or handling of very short inputs.

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

Parameters4/5

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

There is only one parameter and the schema gives it a title ('Source text') plus a 6000-character cap; the description's phrase 'three-word sequences' implies word tokenization of that text, which is a small but real semantic addition. With a single well-typed parameter, the schema does most of the work and the description is not obligated to do more.

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 specific verb and resource: 'Find repeated three-word sequences', with the qualifier 'overlapping windows'. An agent immediately knows this detects n-gram repetition rather than counting words or echoing adjacent words. It stops short of naming or contrasting any sibling (e.g. bpj_adjacent_word_echo, bpj_count_word_frequency), so differentiation is left to inference.

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?

The sentence describes what the tool does but gives no when-to-use guidance, no conditions for choosing it over a sibling like adjacent_word_echo, and no exclusions. The agent must guess that this is the right tool for trigram repetition versus bigram or single-word repetition.

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.