Burs-IA Utils

Buscar caracteres invisibles

text-invisible-scan

Read-onlyIdempotent

Detecta caracteres invisibles (ancho cero, control bidi, etiquetas Unicode) que pueden ocultar instrucciones, y decodifica el texto oculto. Cuándo: hay que transformar, comparar o medir un texto con exactitud y no por aproximación. No para: eliminar caracteres invisibles (text-invisible-strip). Efectos secundarios: ninguno (solo lectura, sin red, sin estado guardado). Determinista: la misma entrada da la misma salida. Límites: entrada JSON de hasta 64 KB, 1 s por llamada, resultado de hasta 1 MB.

EN: Finds zero-width, bidi-control, Unicode tag and other invisible characters (often used to hide instructions in text) and decodes any hidden tag-character text. When: text has to be transformed, compared or measured exactly instead of approximated. Not for: removing zero-width, bidi-control, Unicode tag and other invisible format characters (text-invisible-strip). Side effects: none (read-only, no network access, no stored state). [EN completo / full EN: inputSchema.description]

Input Schema

Name	Required	Description	Default
`text`	Yes	Text (string; required).

Output Schema

Name	Required	Description	Default
`total`	No
`counts`	No
`findings`	No
`hidden_tag_text`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026
- addedInput schema / properties / text / examples
```
Added value: +[
+  "hello"
+]
```

Changed1 schema field changedNov 1, 2026

addedInput schema / description

Added value: +"EN: Finds zero-width, bidi-control, Unicode tag and other invisible characters (often used to hide instructions in text) and decodes any hidden tag-character text. When: text has to be transformed, compared or measured exactly instead of approximated. Not for: removing zero-width, bidi-control, Unicode tag and other invisible format characters (text-invisible-strip). Side effects: none (read-only, no network access, no stored state). Deterministic: the same input gives the same output. Limits: JSON input up to 64 KB, 1 s per call, result up to 1 MB."

First observedNov 1, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnly/openWorld/idempotent/destructive, and the description goes further by adding determinism guarantees and concrete operational limits (input size, 1 s per call, result size). These are exactly the runtime constraints an agent needs and are not derivable from the annotations.

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?

The Spanish text is front-loaded and well structured with labeled When / Not for / Side effects / Deterministic / Limits segments. The trailing full-English restatement duplicates the same content inside a single field, adding bulk without new information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description need not explain return values, and it still covers safety profile, determinism, resource limits and sibling routing. Only the input-size mismatch with the schema slightly undercuts an otherwise complete picture.

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 100% and there is a single required `text` parameter, so the schema already carries parameter meaning and baseline 3 applies. The description adds no parameter-level detail, and its stated 64 KB input limit conflicts with the schema's maxLength of 1,048,576, which could mislead on size.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource pair: detects invisible characters (zero-width, bidi control, Unicode tags) and decodes hidden tag text. It also names the adjacent capability it is not (text-invisible-strip), so the agent can separate the two without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit 'When:' condition (text must be transformed, compared or measured exactly) and an explicit 'Not for:' routing the removal case to text-invisible-strip. Both inclusion and exclusion are stated, which is the top bar for this dimension.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Burs-IA Utils tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?