Skip to main content
Glama

Paragraph lead extraction

bpj_paragraph_topic_lines
Read-onlyIdempotent

Extract the opening sentence of each blank-line-separated paragraph to review structure.

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered structurally. The description adds real behavioral detail beyond that, namely that paragraph boundaries are determined by blank lines and that the output is the opening sentence of each. It omits what happens with a single-paragraph or all-blank-line input and adds nothing about the 6000-character input cap.

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 sentence, front-loaded with the verb and the extraction unit, with the rationale trailing at the end. No redundant restatement of the tool name or title, and nothing could be trimmed without losing meaning.

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

Completeness4/5

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

For a one-parameter read-only tool with no output schema and full annotation coverage, the description supplies the input segmentation rule and the shape of the result, which is what an agent needs to call it correctly. Minor gaps remain around empty or single-paragraph input and the length limit, but nothing essential is missing.

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?

Schema description coverage is 0%, so the description must carry the meaning of the single 'text' parameter, and it does the most important part by defining how that text is segmented into paragraphs and what fragment is returned per paragraph. It does not mention the maxLength of 6000, which leaves one schema constraint unexplained inside the prose.

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 and resource: 'Extract the opening sentence of each blank-line-separated paragraph.' That is precise enough to tell it apart from bpj_paragraph_initials or bpj_paragraph_word_balance, but it never names or characterizes those siblings, so the differentiation is left implicit.

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?

'to review structure' gives an implied usage context, so the agent knows this is a structural-inspection aid rather than a content transform. There is no explicit when-not guidance, no mention of alternatives for other paragraph analyses, and no stated preconditions.

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.