Skip to main content
Glama

Unicode code point escapes

bpj_unicode_escape_sequence
Read-onlyIdempotent

Represent every code point as a JavaScript braced Unicode escape.

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

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 declare this is a read-only, idempotent, closed, non-destructive pure transformation, so the safety profile is covered. The description adds the one behavior that matters beyond that — output is braced escapes per code point — but omits whether ASCII is also escaped, hex casing/padding, and how non-BMP characters are handled.

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?

One tight sentence with no filler, and the key notion (braced Unicode escape) is stated up front. It is perhaps too terse for a format-conversion tool, but nothing is wasted.

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 pure function with a single string input and full annotation coverage, the description covers the essential input-to-output mapping. It leaves unspecified the exact escape rendering (case, zero-padding, ASCII handling) and there is no output schema to fill that gap, so an agent cannot fully predict the returned string format.

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?

With a single parameter whose schema description coverage is 0%, the description is the only place semantics could be added; 'every code point' implies the whole input string is processed rather than a subset. The maxLength=6000 constraint lives only in the schema and the description does not note truncation or rejection behavior for long inputs.

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?

Names a specific transformation (represent every code point) and the exact output notation (JavaScript braced Unicode escape, i.e. \u{...}), so an agent can tell it is a text-to-escape converter. It does not distinguish itself from nearby siblings like bpj_utf16_code_units or bpj_unicode_scalar_inventory, which also operate on code points.

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 statement of when to use this versus the other Unicode/serialization tools, and no prerequisites or exclusions. The agent must infer the use case (producing JS-embeddable escaped output) entirely from the title and description.

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.