Skip to main content
Glama

Read a JSON Pointer

bpj_read_json_pointer
Read-onlyIdempotent

Read an object field or array entry using JSON Pointer. An empty pointer selects the whole value.

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

Input Schema

NameRequiredDescriptionDefault
jsonYes
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 readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds the useful rule that an empty pointer returns the whole value, but says nothing about failure behavior for a missing path or malformed pointer (error vs null), which is the key behavioral unknown for a pointer resolver.

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?

Two tight sentences, front-loaded with the core action, and the second sentence earns its place by defining the empty-pointer edge case. Nothing is redundant, though it is arguably too terse given the zero schema coverage.

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 low-complexity two-parameter tool the core is present, and no output schema means return values need not be described. However, with 0% schema coverage and no annotations about edge cases, the definition should still state the string-encoded input requirement and what happens on unresolvable pointers.

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 must carry parameter meaning. It explains pointer semantics partially (JSON Pointer syntax, empty selects whole value) but never clarifies that 'json' is a serialized JSON string (maxLength 12000) rather than an object, nor the pointer's escaping/format rules.

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 (Read) and resource (object field or array entry) plus the addressing mechanism (JSON Pointer). It does not name a sibling or contrast with adjacent tools like bpj_flatten_json or bpj_check_object_field_contract, so it is clear but not sibling-differentiating.

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 only implied by the mechanics: read a sub-value when you know its pointer. There is no explicit when-to-use/when-not-to-use guidance and no mention of alternatives for extracting nested values, leaving the agent to infer selection.

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.