precedent

Overview Schema Source Related Servers Discussions Admin

query_graph

Read-onlyIdempotent

Run read-only Cypher queries against the precedent graph to retrieve decisions or clauses; capped results indicate truncation.

Instructions

Run a READ-ONLY Cypher query. Rows are capped; a capped result says so in truncated.

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": {
      "cypher": "<cypher>"
    },
    "name": "query_graph"
  }
}

Input Schema

Name	Required	Description	Default
`cypher`	Yes
`max_rows`	No
`parameters`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 13, 2026

TDQS

B3.3/5.0

Behavior4/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description still adds genuinely new behavior: result rows are capped and a capped result is signalled via the `truncated` field, which an agent must know to detect incomplete answers. It omits the default cap value and any cost/timeout considerations.

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 short sentences with zero filler, and the most decision-relevant constraint (READ-ONLY) is front-loaded before the truncation caveat.

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?

An output schema exists, so return shape needn't be spelled out, and the truncation note is a helpful addition. However, for an arbitrary-Cypher execution tool with 0% parameter documentation and a graph_schema sibling that would help authors write valid queries, the definition leaves real gaps about inputs and query preconditions.

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 description coverage is 0% for all three parameters, so the description carries the burden and largely drops it. `cypher`, `max_rows` (default 50) and `parameters` are never explained — notably how `parameters` binds into the query or that `max_rows` interacts with the truncation behavior mentioned.

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 names a specific verb and resource ("Run a ... Cypher query") and qualifies the execution mode as READ-ONLY, which immediately separates it from the decision/link-oriented siblings like propose_decision or explain_link. It does not explicitly name a sibling it replaces, so it falls short of a 5.

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 statement of when to reach for this tool versus graph_schema (for discovering labels/relationships) or search_decisions (for lookup-style retrieval). The only implicit guidance is that the query must be read-only; nothing tells the agent what kinds of questions this tool is the right answer for.

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

Deploy Server