Skip to main content
Glama

Bidirectional field isolation

bpj_bidi_isolate_fields
Read-onlyIdempotent

Wrap each nonempty field with Unicode FSI/PDI isolates and include an escaped representation for inspection.

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real facts beyond that: only nonempty fields are wrapped, and the output includes an escaped representation for inspection. It still omits the output shape, how many fields are expected, and whether non-ASCII or already-isolated text is 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?

A single tight sentence with no filler and the mechanism front-loaded. Concision is good, though the brevity contributes to the ambiguity around 'fields' rather than resolving it.

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 transform tool with one undocumented parameter and no output schema, the description should specify how fields are delimited, what the escaped representation looks like, and edge cases such as empty or already-isolated input. Almost none of that is present, so the definition is not complete enough to call reliably.

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 description coverage is 0% for the single parameter, so the description carries the burden and does not meet it. It never explains what the 'text' string should contain, how it maps to 'fields', or the maxLength 6000 constraint, leaving the relationship between input and the wrapped units undefined.

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

Purpose3/5

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

The verb ('wrap with FSI/PDI isolates') and the Unicode mechanism are specific, but the object ('each nonempty field') is ambiguous because the schema accepts a single string called 'text', not a collection of fields. The definition never explains how 'fields' are derived from the input, so the agent cannot fully predict what the tool does.

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 tool, when not to, or how it relates to any alternative such as table or JSON field handling siblings. Usage must be fully inferred from the name and one-line 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.