Skip to main content
Glama

Parse JSON pointer segments

bpj_json_pointer_segments
Read-onlyIdempotent

Validate RFC 6901 escape sequences and recover the original key segments.

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": {
      "pointer": "<pointer>"
    },
    "name": "bpj_json_pointer_segments"
  }
}

Input Schema

NameRequiredDescriptionDefault
pointerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare the operation read-only, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds that validation occurs against RFC 6901 escapes and that segments come back unescaped, which is genuine behavioral context. It stops short of saying what happens on an invalid pointer (error vs. partial result) or what the returned structure looks like.

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 sentence, no filler, with the validation behavior front-loaded ahead of the output. It is efficient and readable; the only shortfall is that brevity here borders on under-specification rather than crispness.

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?

This is a simple single-parameter tool with no output schema and strong annotations, so it does not need a long description. Still, an agent would benefit from knowing the return shape (ordered segment list) and error behavior for malformed pointers, neither of which is stated.

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 coverage is 0%, so the description carries the burden, and the RFC 6901 reference is meaningful — it tells the agent the input uses ~0/~1 escape conventions and slash-delimited tokens. It does not clarify whether a leading slash is required, what an empty string means, or how the 500-character limit interacts with nesting depth, so the compensation is partial.

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?

The description names two concrete operations on a specific resource: validate RFC 6901 escape sequences and recover the original key segments from a pointer. That is more than a restatement of the title and tells an agent what the call produces. It does not, however, distinguish itself from siblings like bpj_json_pointer_encode or bpj_read_json_pointer, which handle the inverse operation and value lookup respectively.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: an agent can infer this is the tool for turning a pointer string into its constituent keys, with validation as a side effect. There is no explicit when-to-use, no exclusion, and no pointer to the encode/read siblings as alternatives, so the agent must infer routing from names alone.

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.