Skip to main content
Glama

Number text lines

bpj_number_text_lines
Read-onlyIdempotent

Prefix each line with an aligned decimal line number from a chosen starting value.

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>",
      "start": "<start>"
    },
    "name": "bpj_number_text_lines"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
startYes

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 readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is covered. The description adds the genuine behavioral trait that numbering is padded/aligned and starts at a caller-chosen value. It still omits how the alignment width is derived (e.g. width of the largest resulting number) and whether line endings or a trailing empty line are preserved.

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 operative verb, with zero redundant or filler wording. Nothing could be removed without losing meaning.

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-only text transformation, most of what an agent needs is present, and the annotations cover safety. Gaps remain around the exact output layout (padding width rule, handling of empty lines) and the input size limit, which matter when composing the call and parsing the result.

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% – only bare titles exist – so the description has to carry the meaning of both parameters, and it does partially: 'each line' maps to text and 'chosen starting value' maps to start. It adds no detail on the 6000-character cap, the 0–999999 range, or how start affects the padded column width.

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 ('Prefix') and resource ('each line') plus the output quality ('aligned decimal line number') and the configurable start value, so the operation is unambiguous. It does not name or contrast any sibling transformation tool, which keeps it short of a 5.

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 / when-not-to-use guidance and no mention of alternatives among the many bpj_* line-processing tools. The agent must infer that this is the tool for adding line numbers rather than for inspecting, deduplicating or searching 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.