Skip to main content
Glama

binary-forensics

unicode_inspect

Inspect every Unicode code point in text for zero-width joiners, bidirectional Trojan Source overrides, homoglyph spoofing, and UTF-8/UTF-16 byte encodings.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "unicode_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoText string to audit at code-point level.
filePathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations at all, the description carries the full burden, and it discloses only what is detected, not how the tool behaves. It never says whether inspection is read-only, whether it can read from disk, whether findings are reported with offsets/spans, whether there are size limits, or what the response looks like (there is no output schema to fall back on).

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 no filler; every clause names a distinct detection capability. Nothing needs to be trimmed.

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

Completeness2/5

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

For a tool with two input modes, zero annotations, no output schema, and one entirely undocumented parameter, the description is too thin. It omits file-input handling, output format, and any operational constraints, leaving the agent to guess how to invoke it correctly and what it will return.

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 coverage is 50%: 'text' is documented in the schema, but 'filePath' is undocumented in both the schema and the description. The description speaks only of inspecting 'text' and never mentions that a file path is an accepted input, so an agent cannot know the two parameters are alternative input sources.

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?

Names a specific verb and resource ('Inspect every Unicode code point in text') and enumerates the exact threat classes it looks for: zero-width joiners, bidirectional Trojan Source overrides, homoglyph spoofing, and byte encodings. That vocabulary alone separates it from siblings like hexdump_inspect or binary_triage without opening either schema.

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 statement, and no alternative tool is named. Usage is only implied by the term 'audit' and the security-focused detection list; an agent must infer that this is for untrusted text suspected of spoofing rather than general encoding conversion.

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.

Resources