Skip to main content
Glama

Keyword concordance

bpj_keyword_in_context_lines
Read-onlyIdempotent

Build a concordance of whole-word matches with up to five words on either side.

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

Input Schema

NameRequiredDescriptionDefault
textYes
wordYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 substantive behavior of whole-word matching and a bounded context window, but is silent on case sensitivity, what happens with overlapping or repeated matches, and what the returned concordance actually looks like (no output schema exists to cover that).

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 operation, matching rule and window are all packed into it.

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 two-parameter, closed-world read tool this covers the core operation, but with no output schema the description should at least sketch the return shape (matched lines with highlighted keyword?) and state case sensitivity. Those gaps are real but modest given the tool's simplicity.

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?

Schema description coverage is 0% for both parameters, so the description must carry the load; it does partially by clarifying that `word` is matched as a whole word and that context extends up to five words per side. It does not tie `text` to the 6000-char cap or specify case folding, so the 100-char keyword and match semantics remain ambiguous.

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 gives a specific verb and output artifact ("build a concordance") plus the matching rule (whole-word) and window size (±5 words), which is enough to distinguish it from a plain line-search or plain surrounding-lines tool. It stops short of naming any sibling to sharpen the boundary.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer it is for keyword-in-context lookups rather than distribution counting or raw text search, given the sibling names. There is no explicit when-to-use statement and no exclusions pointing to bpj_search_text_context or bpj_surrounding_lines.

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.