Skip to main content
Glama

TestingAPIs API tools

Run a JSONPath query

query_jsonpath
Read-onlyIdempotent

Evaluate a JSONPath expression (RFC 9535: filters like $..book[?@.price < 10], slices, recursive descent, length/count/match/search) against JSON. Returns each match with its normalized path.

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>",
      "path": "<path>"
    },
    "name": "query_jsonpath"
  }
}

Input Schema

NameRequiredDescriptionDefault
jsonYesThe JSON to search.
pathYesThe JSONPath, starting with $.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds value beyond the annotations by disclosing the return shape ('each match with its normalized path'), which is important because no output schema exists.

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

Conciseness5/5

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

Two dense sentences with the operation and dialect stated first and the return behavior second; every clause carries information (standard, example, feature list, return format) and nothing is redundant.

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?

For a simple two-parameter read-only tool, the description covers input semantics, dialect scope, and return shape without an output schema. The only minor gap is that it does not mention edge-case behavior such as no-match results or error handling for invalid expressions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description goes further by specifying the supported dialect (RFC 9535 with filters, slices, recursive descent, length/count/match/search), which clarifies what the 'path' parameter accepts beyond the terse schema note 'starting with $'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Evaluate a JSONPath expression ... against JSON'), names the standard (RFC 9535), and gives a concrete filter example, so an agent can distinguish it from validate_json_schema or compare_json without opening the schema.

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?

The tool's purpose is clear, but there is no explicit when-to-use/when-not-to-use guidance and no routing to alternatives such as compare_json or generate_json_schema. Usage is implied by the purpose rather than stated.

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.

Resources