Skip to main content
Glama

Line indentation profile

bpj_indentation_profile
Read-onlyIdempotent

Count nonblank lines by space, tab, mixed or absent indentation.

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety needs no further disclosure. The description adds the key scoping fact that blank lines are excluded and that each line is assigned to exactly one of four categories (mutually exclusive classification), which is useful beyond the annotations, but it says nothing about the output shape or the maxLength=6000 input limit.

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 a verb, resource, and the four categories, with no redundant or filler wording. Nothing needs trimming and nothing is buried.

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 counting tool with no output schema, the description conveys the essential classification semantics. Minor gaps remain around return format and input-size limits, but the tool is simple enough that these are not blocking.

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 only one parameter ('text'), and schema description coverage is 0%, so the description would need to clarify it. It implicitly says the input is source text containing lines to classify, which is a mild gain, but the 6000-character cap and behavior on oversized or empty input are left entirely to the schema and annotations.

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') plus the resource ('nonblank lines') and the classification axis (space, tab, mixed, absent indentation), which is enough to distinguish it from length- or width-oriented siblings. It does not explicitly name a sibling alternative, but the resource is concrete and unambiguous.

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?

The description implies the use case (profiling indentation style) but never states when to reach for this tool versus e.g. line-length or whitespace siblings, nor any preconditions. There are no exclusions or alternatives, so routing relies on the agent inferring from the name and count semantics.

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.