Skip to main content
Glama
MCP Toolkit

MCP Toolkit

json_pointer

Retrieve a value from JSON using an RFC 6901 JSON Pointer to navigate nested objects and arrays without manual parsing.

Instructions

Look up a value in JSON using an RFC 6901 JSON Pointer.

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": "json_pointer"
  }
}

Input Schema

NameRequiredDescriptionDefault
jsonYes
pointerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not say what happens when the pointer does not resolve (error vs null), whether the input is serialized JSON text or an already-parsed document, or whether RFC 6901 escape sequences (~0, ~1) are handled. Only the non-mutating nature is implied by 'look up'.

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, so nothing needs trimming. It is arguably under-sized rather than over-sized, but the structure itself is clean.

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 two-parameter lookup tool with no output schema, the definition is close to adequate: the operation and the pointer standard are identified. The missing pieces are error/failure semantics and the string-encoded nature of the 'json' input, which matter for correct invocation.

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 description coverage is 0% for both parameters, so the description must compensate, and it partially does: the RFC 6901 reference gives real meaning and syntax to the 'pointer' argument beyond a bare string. However, it never explains that 'json' is a string containing serialized JSON (and not an object), which is the main ambiguity for a caller.

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 and resource ('Look up a value in JSON') plus a precise standard ('RFC 6901 JSON Pointer'), which clearly separates it from siblings like json_format or json_inspect that transform or describe documents. It stops short of naming a sibling explicitly, but the operation itself is unambiguous.

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 guidance on when to choose this over json_inspect or json_format, and no note that this is the tool for extracting a single nested value rather than describing the whole document. The usage is only inferable from the verb 'look up'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.