Skip to main content
Glama

Adjacent repeated words

bpj_adjacent_word_echo
Read-onlyIdempotent

Find adjacent English words repeated across whitespace, ignoring case.

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 genuinely useful matching behavior beyond that: case-insensitive comparison and adjacency across whitespace. It does not disclose what the result contains (match list, counts, positions), which matters since there is no output schema.

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?

One front-loaded sentence with no filler; every clause (adjacent, English, whitespace, ignoring case) carries operative meaning.

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 simple one-parameter text scanner with no output schema, the definition covers input semantics adequately but leaves the return value and overlap-handling rules unexplained. Given annotations cover the safety profile, this is borderline adequate rather than complete.

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

Parameters2/5

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

Schema description coverage is 0% — the single 'text' parameter has no documented meaning in the schema. The description only indirectly implies the parameter holds English prose subject to whitespace tokenization; it says nothing about the 6000-character limit, trimming, or accepted input form, so it fails to compensate for the coverage gap.

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 ('Find') and a precise resource ('adjacent English words repeated across whitespace, ignoring case'). The matching semantics (adjacency, whitespace boundary, case-insensitivity) clearly distinguish it from a broader repeated-word or trigram tool, though no sibling is named.

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 description never says when to use this versus alternatives such as the repeated-trigram or frequency-count siblings, nor does it state any prerequisites or exclusions. The only guidance is implied by the matching conditions themselves.

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.