Skip to main content
Glama

Long sentence shortlist

bpj_long_sentence_shortlist
Read-onlyIdempotent

List sentences exceeding a chosen word count, preserving sentence numbers.

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>",
      "limit": "<limit>"
    },
    "name": "bpj_long_sentence_shortlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
limitYes

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 the read-only, idempotent, closed-world, non-destructive profile, so safety disclosure is covered. The description adds the useful behavioral detail that original sentence numbers are retained in the output, but says nothing about output shape, ordering, or what an empty result looks like.

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 compact sentence, front-loaded with the action and the filter condition, with the retention note placed after. Nothing is redundant.

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 two-parameter read tool with rich annotations and no output schema, the definition covers the essentials but leaves gaps: exact threshold semantics, output field structure, and result ordering are unstated. Adequate, not complete.

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%, so the description must carry the load: it does clarify that the integer is a word-count threshold and that filtering is on sentences "exceeding" it, which pins down the comparison direction. It adds no detail on the source-text parameter's size cap (maxLength 6000) or on boundary behavior (strictly greater vs. greater-or-equal).

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 states a specific verb ("List") and resource ("sentences exceeding a chosen word count") and adds an output trait ("preserving sentence numbers") that separates it from a mere length profile like bpj_sentence_length_profile. It is clear on its own, though it never names the sibling it contrasts with.

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 when-to-use guidance and no mention of alternatives. An agent cannot tell from this text whether to reach for this shortlist tool or the length-profile sibling when it wants sentence-length information.

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.