Skip to main content
Glama

Remove common indentation

bpj_strip_common_indent
Read-onlyIdempotent

Remove the longest identical leading whitespace prefix shared by all nonblank lines.

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered by structured data. The description adds genuine semantic detail beyond that: it clarifies that the common prefix is computed only over nonblank lines and must be shared by all of them, which resolves the main ambiguity of "common indent." It does not describe return behavior or edge cases such as text with no common indent or all-blank input.

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?

The description is a single front-loaded sentence with no filler; every clause sharpens the definition of the common prefix.

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 pure string transform with annotations covering safety, the core semantics are adequately conveyed, but there is no output schema and the description does not state that a string is returned, nor how blank lines, mixed tabs/spaces, or empty input are handled.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single required parameter, which surfaces only as "text" with the title "Source text" and a maxLength of 6000. The description never mentions the parameter, the 6000-character cap, or whether the input is raw text versus lines, so it does not compensate for the coverage gap.

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 ("Remove") and a precise definition of the resource ("the longest identical leading whitespace prefix shared by all nonblank lines"), which is far more precise than the title alone. It does not distinguish itself from the sibling bpj_indentation_profile, which plausibly operates on the same input, so it falls 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 statement of when to use this tool versus an alternative such as bpj_indentation_profile, nor any prerequisites or exclusions. The use case (dedenting a block of text) is only inferable from the operation 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.