Skip to main content
Glama

Keyword distribution by quarter

bpj_keyword_distribution_quartiles
Read-onlyIdempotent

Split token positions into four quarters and count occurrences of the target word in each.

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>",
      "word": "<word>"
    },
    "name": "bpj_keyword_distribution_quartiles"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
wordYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds the core computation (four quarters over token positions), but says nothing about tokenization rules, case sensitivity, or what the result looks like beyond four counts. No annotation contradiction exists.

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?

A single tight sentence with no filler, and the operation is front-loaded. The phrase 'token positions' is slightly compressed and is the source of the ambiguity, but nothing is wasted.

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

Completeness2/5

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

With no output schema, no parameter descriptions, and only a one-line description, an agent cannot predict the result shape (four labeled counts? an array?) or the tokenization behavior that determines those counts. For a two-parameter analysis tool this leaves too much unresolved.

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%, so the only parameter documentation is the bare titles 'Source text' and 'Target word' plus maxLength. The description hints that text is tokenized and that the word is matched as a whole token, but it leaves critical details open: how tokens are delimited, whether matching is case-sensitive, and whether partial or substring matches count.

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 operation: splitting token positions into four quarters and counting target-word occurrences in each. That is more than a restatement of the name and tells an agent concretely what is computed. It stops short of distinguishing this from related siblings such as bpj_keyword_in_context_lines or bpj_table_group_quartiles.

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 statement of when to use this tool, when not to, or which sibling to prefer for keyword counting versus keyword context. The agent must infer the use case entirely from the operation described.

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.