Skip to main content
Glama

Paragraph initials index

bpj_paragraph_initials
Read-onlyIdempotent

Collect the first grapheme of each blank-line-separated paragraph in reading order.

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds the useful detail that extraction is grapheme-aware and reading-order preserving, but omits the return shape (list vs joined string), handling of whitespace-only or empty paragraphs, and behavior on truncation.

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?

One compact sentence with the scope and ordering constraint front-loaded; nothing is padded. Slightly under-specified rather than verbose, which is the right failure direction for this size.

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 one-parameter, annotation-covered tool this is close to adequate, but with no output schema the description should say what comes back (array of one-character strings? count?) and how empty paragraphs are handled. Those gaps leave the agent guessing at the result shape.

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% and the single 'text' parameter carries only a title and maxLength. The description does supply real meaning by defining the segmentation rule (blank-line-separated paragraphs) that governs how the input is interpreted, but it never mentions the 6000-character cap or whether the whole document must be passed at once.

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?

Specific verb ('Collect') plus a precisely defined resource ('first grapheme of each blank-line-separated paragraph in reading order'). It clearly separates itself from something like bpj_citation_initials by naming the segmentation unit (blank-line-separated paragraphs), though it never explicitly contrasts with a sibling.

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, no preconditions, and no pointer to a related sibling (e.g. citation initials vs paragraph initials). Usage is only inferable from the purpose statement itself.

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.