Skip to main content
Glama

Visible whitespace preview

bpj_visible_whitespace_preview
Read-onlyIdempotent

Render spaces, tabs, line breaks and nonbreaking spaces with visible markers.

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

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 establish that this is a read-only, idempotent, non-destructive, closed-world operation, so the safety profile is covered. The description adds the useful scope detail of which character classes are visualized, but says nothing about what the markers actually look like (e.g. · vs → vs ¶) or the shape of the rendered output, which is the key behavioral fact for a preview tool.

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?

A single front-loaded sentence with no filler or redundancy. Its terseness is efficient, though it leaves real gaps unaddressed rather than being genuinely complete.

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, read-only preview tool with annotations covering safety and no output schema, the description is minimally adequate. It is missing the two things an agent would most want to know: what the marker convention is and what the returned preview looks like, which matters because there is no output schema to fall back on.

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 a single required parameter with 0% schema description coverage, so the description would ideally explain the input. The name 'text' plus the title 'Source text' make the parameter largely self-evident, and the description's mention of character classes implies what content is expected, but the 6000-character limit and any input handling expectations are never surfaced.

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 concrete verb plus the exact character classes handled (spaces, tabs, line breaks, nonbreaking spaces) rendered as visible markers, which is more specific than the title alone. It does not explicitly contrast itself with whitespace siblings like bpj_normalize_whitespace, so the agent must infer the difference from the verb 'render... visible markers'.

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 explicit when-to-use or when-not-to-use guidance, and no alternative is named. An agent can only infer from the verb that this is a diagnostic/inspection tool, and could easily confuse it with the normalization or padding-whitespace siblings sharing the same subject matter.

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.