Tools for agents: Batch JSON Pointer lookup

Connect with MCP

{
  "mcpServers": {
    "super-agent-tools": {
      "url": "https://app.getsupers.com/sites/agent-json-pointer/mcp"
    }
  }
}

Use this URL in any client supporting remote Streamable HTTP MCP. Calls return structured JSON; inputs are processed without persistence.

Call resolve_json_pointers

Uses the RFC 6901 JSON string form: empty string selects the root; slash separates tokens; ~1 means slash and ~0 means tilde. URI fragments beginning # are not accepted and percent escapes are not decoded. Object keys are exact and never normalized. Arrays require zero-based ASCII indices without leading zeros. The dash array token refers to a nonexistent append position and cannot be read. Each requested pointer produces one ordered result, including duplicates. Check found: a successful null includes value:null; an unresolved pointer omits value and includes an error. token_index is zero-based and identifies the first failing decoded token. Invalid pointer syntax is reported per item without aborting other lookups. Input is an already parsed JSON value, so duplicate keys discarded by an upstream parser cannot be recovered. No writes, wildcard queries, expression evaluation or remote fetching occurs. Specification: https://www.rfc-editor.org/rfc/rfc6901

{
  "name": "resolve_json_pointers",
  "title": "Batch JSON Pointer lookup",
  "description": "Resolve JSON Pointer strings without modifying the document. Return found/value or a per-pointer error; null is a successful value. URI-fragment form is not supported.",
  "inputSchema": {
    "$defs": {
      "JsonValue": {}
    },
    "properties": {
      "document": {
        "$ref": "#/$defs/JsonValue"
      },
      "pointers": {
        "items": {
          "type": "string"
        },
        "title": "Pointers",
        "type": "array"
      }
    },
    "required": [
      "document",
      "pointers"
    ],
    "title": "resolve_json_pointersArguments",
    "type": "object"
  },
  "outputSchema": {
    "additionalProperties": true,
    "title": "resolve_json_pointersDictOutput",
    "type": "object"
  },
  "icons": null,
  "annotations": {
    "title": null,
    "readOnlyHint": true,
    "destructiveHint": false,
    "idempotentHint": true,
    "openWorldHint": false
  },
  "meta": null,
  "execution": null
}

Run the example to see the actual result.

HTTP alternative

POST https://app.getsupers.com/sites/agent-json-pointer/call
Content-Type: application/json

{
  "document": {
    "agents": [
      {
        "name": "builder",
        "result": null
      }
    ],
    "a/b": {
      "~key": 42
    }
  },
  "pointers": [
    "/agents/0/name",
    "/agents/0/result",
    "/agents/1",
    "/a~1b/~0key"
  ]
}

The HTTP and MCP interfaces execute the same implementation. Validation errors are returned explicitly. See the tool notes above for its supported inputs and behavior.