Skip to main content
Glama

data-api-code

jsonpath_query_eval

Evaluate JSONPath / dot-path expressions (including $, wildcards *, array indices, and recursive descent ..) over any JSON document.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "jsonpath_query_eval"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataNo
textNo
jsonPathNo$.items[*].name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full burden and says nothing about error behavior on malformed paths, whether a single value or a list of matches is returned, or whether missing matches raise or yield empty results. "Over any JSON document" hints at broad input tolerance but is the only behavioral disclosure.

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; the parenthetical syntax list is informative rather than padding. It is compact without being cryptic.

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

Completeness2/5

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

For a tool with no annotations, no output schema, and three undocumented parameters, the description is too thin — most importantly it never explains the input document parameter choice or the return shape. The stated purpose is clear but the operational details an agent needs to invoke it correctly are missing.

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

Parameters2/5

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

Schema coverage is 0% and the schema itself is nearly empty (data has no type, text is a bare string, jsonPath has only a default). The description clarifies the jsonPath syntax ($, wildcards, indices, recursive descent) but leaves the critical ambiguity between the `data` and `text` parameters completely unaddressed — an agent cannot tell which one supplies the document.

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 states a specific verb ("Evaluate") and resource ("JSONPath / dot-path expressions ... over any JSON document"), which clearly separates it from siblings like json_structural_diff or json_to_csv_convert. It stops short of naming or contrasting any alternative tool, which keeps it out of the 5 tier.

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 prefer this tool over the many other JSON-related siblings, nor any prerequisites or exclusions. The only implicit signal is that it evaluates paths rather than transforming or validating documents.

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