Skip to main content
Glama

Build a JSON pointer

bpj_json_pointer_encode
Read-onlyIdempotent

Encode path segments as an RFC 6901 pointer with slash and tilde escaping.

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": {
      "keys": "<keys>"
    },
    "name": "bpj_json_pointer_encode"
  }
}

Input Schema

NameRequiredDescriptionDefault
keysYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/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 a closed world, so the safety profile is covered. The description adds genuine behavioral content by naming slash and tilde escaping per RFC 6901, which tells the agent how output is transformed. It says nothing about the return value (presumably a string) or how empty/invalid segments 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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though the terseness contributes to the gaps noted in parameter semantics rather than being purely a strength.

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 one-parameter utility with annotations and no output schema, the description need not explain return values. However, it omits the input encoding convention (a JSON array serialized into a string) and any hint of ordering or empty-segment handling, which are the details an agent is most likely to get wrong.

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%, so the description must carry the burden, and it does not. It says 'path segments' while the schema defines a single string parameter titled 'JSON array of field names' with maxLength 1500 — the description never clarifies that the segments are supplied as a JSON-encoded array string, which is the main ambiguity an agent would hit.

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?

States a specific verb ('Encode') and a concrete resource ('path segments as an RFC 6901 pointer') with the escaping rule named, so an agent knows exactly what the tool produces. It does not differentiate from nearby siblings such as bpj_json_pointer_segments (the apparent inverse) or bpj_read_json_pointer, leaving the choice between them to inference.

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 when-to-use guidance, no prerequisites, and no mention of an alternative. The purpose implies a narrow utility (building a pointer before a read/patch call), but the agent must infer that a pointer is the prerequisite for other sibling tools rather than being told.

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.