NeoCoder Neo4j AI Workflow

list_cypher_snippets

Retrieve reusable Cypher code snippets with optional filters by tag, version, or pagination to support Neo4j workflows.

Instructions

List all available Cypher snippets with optional filtering.

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": "list_cypher_snippets"
  }
}

Input Schema

Name	Required	Description	Default
`tag`	No
`limit`	No
`offset`	No
`since_version`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Aug 7, 2026

TDQS

C2.4/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not mention that this is a read-only operation, nor does it describe pagination, sorting, or the response format. The phrase 'optional filtering' hints at behavior but lacks specifics.

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 description is a single concise sentence that conveys the core purpose. However, it is under-specified, bordering on terse, as it omits important details such as the available filters. It is not excessively wordy, but it sacrifices clarity for brevity.

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 4 parameters, no schema descriptions, and no annotations, the description is insufficiently complete. It fails to explain the filtering options, pagination behavior, or the nature of the returned snippets. The presence of an output schema does not cover usage semantics.

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

Parameters1/5

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

The input schema has 4 parameters with 0% description coverage, so the description must compensate by explaining the filtering criteria and pagination. However, it only says 'optional filtering' without naming tag, since_version, limit, or offset. No additional meaning is provided beyond the schema's defaults.

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 action (List) and resource (all available Cypher snippets) with optional filtering. It is specific enough to understand the basic purpose, though it does not explicitly distinguish from sibling 'search_cypher_snippets'.

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?

The description provides no guidance on when to use this tool versus alternatives such as search_cypher_snippets or get_cypher_snippet. It does not mention context, prerequisites, or exclusions.

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