Lordevo Shop (x402 website checks)

JSON query: JSONPath (RFC 9535) or JSON Pointer ($0.002/call)

json_query

Read-onlyIdempotent

$0.002 per call (x402, USDC on Base; free trial: add "trial": true or use try_free). [Data utilities] Selects values from a JSON document with a JSONPath query (RFC 9535: names, indexes, slices, wildcards, .. descendants, filters with comparisons, && || ! and length/count/value) or a JSON Pointer (RFC 6901). Returns every match with its normalized path and pointer. Input: json and query (POST for large documents), optional max_results. Limits: 1 MB JSON, 1,000-character query; match() and search() are not offered. Offline.

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>",
      "query": "<query>"
    },
    "name": "json_query"
  }
}

Input Schema

Name	Required	Description	Default
`json`	Yes	JSON text, up to 1 MB (a JSON value is also accepted in a POST body or MCP arguments)
`query`	Yes	JSONPath starting with $ (RFC 9535, e.g. $.items[?@.price < 10].name) or JSON Pointer starting with / (RFC 6901, e.g. /items/0/name)
`trial`	No	Optional. true = free if a trial call is left (3 per IP per UTC day), else the payment terms.
`max_results`	No	Values returned, 1-1000 (default 100); match_count is always the full count	100

Output Schema

Name	Required	Description
`tool`	No
`cache`	No
`notes`	No
`query`	No
`_trial`	No	Present when the call was a free trial call.
`results`	No
`language`	No
`provider`	No
`price_usd`	No
`truncated`	No
`match_count`	No
`results_returned`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 5, 2026

changedInput schema / properties / trial / description

Previous value: -"Optional. true = answer free if a trial call is left (3 per IP per UTC day); otherwise you get the payment terms."New value: +"Optional. true = free if a trial call is left (3 per IP per UTC day), else the payment terms."

Changed2 schema fields changedNov 3, 2026

addedInput schema / properties / trial

Added value: +{
+  "description": "Optional. true = answer free if a trial call is left (3 per IP per UTC day); otherwise you get the payment terms.",
+  "type": "boolean"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "anyOf": [
+    {
+      "required": [
+        "tool",
+        "language",
+        "match_count",
+        "results"
+      ]
+    },
+    {
+      "properties": {
+        "accepts": {
+          "type": "array"
+        },
+        "error": {
+          "type": "string"
+        },
+        "resource": {
+          "type": "object"
+        },
+        "x402Version": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "x402Version",
+        "accepts"
+      ]
+    },
+    {
+      "properties": {
+        "charged": {
+          "type": "boolean"
+        },
+        "error": {
+          "type": "string"
+        },
+        "message": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "error"
+      ]
+    }
+  ],
+  "properties": {
+    "_trial": {
+      "description": "Present when the call was a free trial call.",
+      "type": "object"
+    },
+    "cache": {
+      "type": "object"
+    },
+    "language": {
+      "enum": [
+        "jsonpath",
+        "json-pointer"
+      ],
+      "type": "string"
+    },
+    "match_count": {
+      "type": "integer"
+    },
+    "notes": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "price_usd": {
+      "type": "number"
+    },
+    "provider": {
+      "type": "string"
+    },
+    "query": {
+      "type": "string"
+    },
+    "results": {
+      "items": {
+        "properties": {
+          "path": {
+            "type": "string"
+          },
+          "pointer": {
+            "type": "string"
+          },
+          "value": {}
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "results_returned": {
+      "type": "integer"
+    },
+    "tool": {
+      "type": "string"
+    },
+    "truncated": {
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

AddedNov 2, 2026

TDQS

A4/5.0

Behavior5/5

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

Annotations already cover the safety profile (read-only, idempotent, non-destructive, closed-world), and the description still adds substantial operational context: per-call pricing via x402 in USDC on Base, a free-trial mechanism with its own parameter, hard limits of 1 MB of JSON and 1,000 characters of query, and an explicit statement that match()/search() are unsupported. The 'Offline' note further clarifies that the result comes from a local computation rather than a network fetch.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is dense and single-paragraph, but it leads with pricing rather than purpose, so the agent has to read past a billing clause before learning what the tool does. Several clauses (1 MB JSON, 1,000-character query, max_results) duplicate the schema verbatim and could be trimmed, though nothing is truly wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and the description still notes that every match comes back with its normalized path and pointer. Limits, transport guidance, unsupported functions, and pricing are all covered; only edge behavior on malformed JSON or an invalid pointer is left unstated.

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 100% and the schema already documents json, query syntax, trial semantics, and max_results including the 1-1000 range and the 'match_count is always the full count' caveat. The description largely restates those same limits, with the only genuinely new parameter-level detail being that large documents can be submitted via POST; that is a modest addition over an already complete schema.

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 gives a specific verb and resource — 'Selects values from a JSON document' — and pins down the two query dialects (RFC 9535 JSONPath, RFC 6901 JSON Pointer), which clearly separates it from siblings like json_validate, json_repair, and json_schema_infer. It stops short of naming those siblings or stating an explicit routing rule, so it is clear but not maximally differentiating.

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

Usage Guidelines4/5

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

It tells the agent which query syntax to reach for (path starting with $ vs pointer starting with /), when to switch to POST for large documents, and what is explicitly out of scope (match() and search() not offered). It does not say when to prefer a sibling tool such as json_validate or structural extraction, but the usage context is otherwise concrete.

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

All Lordevo Shop (x402 website checks) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?