NeoCoder Neo4j AI Workflow

run_custom_query

Execute custom Cypher queries to perform advanced operations on Neo4j knowledge graphs, enabling precise data retrieval and manipulation.

Instructions

Run a custom Cypher query for advanced operations.

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

Input Schema

Name	Required	Description	Default
`query`	Yes	Custom Cypher query to execute
`params`	No	Query parameters

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Aug 7, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions running a custom query but does not disclose that arbitrary Cypher can mutate data, delete records, or have side effects, nor does it mention permission requirements. This is a significant gap for a potentially destructive tool.

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?

The description is a single sentence with no filler, front-loading the action. However, it is so minimal that it lacks richness. Still, it is appropriately sized for a simple tool, so it earns a 4.

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?

Given the tool's ability to execute arbitrary Cypher, the description is incomplete. It lacks warnings about side effects, guidance on parameter use, and when to invoke this tool versus safer alternatives. Even though the schema covers parameters and output, the contextual risk profile is not addressed.

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?

The input schema fully documents both parameters (query and params), so the baseline is 3. The description adds no additional meaning beyond the schema, such as how params are used or examples. Therefore, the score remains at the baseline.

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 clearly states the tool runs a custom Cypher query, using a specific verb and resource. It distinguishes itself as a general-purpose query runner for advanced operations, but does not explicitly contrast with siblings like write_neo4j_cypher.

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 phrase 'for advanced operations' implies usage for scenarios beyond standard tool capabilities, but it offers no explicit guidance on when to choose this over alternatives such as write_neo4j_cypher or standard CRUD tools. There are no exclusions or prerequisite conditions.

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