Skip to main content
Glama

Find invisible control characters

bpj_find_invisible_characters
Read-onlyIdempotent

Locate invisible formatting controls, nonbreaking spaces and other uncommon separators.

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

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?

Annotations already cover safety behavior: read-only, non-destructive, idempotent, and closed-world. The description adds detection scope by naming the kinds of characters found, but it does not explain the return format or how matches are reported.

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?

It is a single front-loaded sentence with no filler, and every phrase contributes to describing the detection scope. The structure is clean and appropriately sized.

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 read-only finder, the description identifies what is detected and the annotations cover safety. However, with no output schema, it leaves the result shape unexplained, such as whether it returns positions, counts, or cleaned text, making it minimally usable but incomplete.

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?

The tool has one required 'text' parameter, and schema description coverage is 0%. The description never mentions the parameter or clarifies that the supplied text is what will be scanned, adding no meaning beyond the schema's type, title, and maxLength.

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 states a specific verb ('Locate') and specific targets (invisible formatting controls, nonbreaking spaces, uncommon separators), so the operation is clear. It does not explicitly contrast with any sibling tool, so it is clear but not fully differentiated.

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 guidance about when to use this tool, when not to use it, or what alternative might apply. The purpose only implies a use case, leaving the agent to infer selection conditions.

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.