Skip to main content
Glama

Line ending inventory

bpj_newline_inventory
Read-onlyIdempotent

Count CRLF, LF and CR line endings and detect a final newline.

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 behavior, so the safety profile is covered. The description adds a little behavioral detail by naming three distinct newline kinds counted separately (so CRLF is not conflated with CR or LF) and the final-newline check. It says nothing about the 6000-character input cap, error behavior, or return shape.

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; every clause (three newline types, final newline) carries information the agent needs.

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 simple single-input analyzer with no output schema, this is nearly complete: the agent knows what is counted and what is detected. The only gaps are the unmentioned input length limit and no hint about the result format (counts per type plus a boolean).

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?

There is one parameter, text, whose name and title ('Source text') are largely self-explanatory, but schema description coverage is 0% and the description does not mention the input at all. It neither clarifies what text is expected (raw file content vs. snippet) nor warns that inputs over 6000 characters are rejected.

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 (count) and resource (CRLF, LF and CR line endings) plus an extra behavior (detect a final newline). That distinguishes it from sibling line-oriented tools like bpj_line_length_distribution or bpj_subtitle_line_width_review, though it never names an alternative explicitly.

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 or when-not-to-use guidance and no mention of alternative tools. The agent must infer from the purpose alone that this is the tool for newline/line-ending analysis rather than line length or width checks.

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.