NeoCoder Neo4j AI Workflow

list_action_templates

List and filter current action templates by keyword to find standardized coding workflows for AI-assisted development.

Instructions

List all available action templates.

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_action_templates"
  }
}

Input Schema

Name	Required	Description	Default
`keyword`	No	Filter by specific keyword
`current_only`	No	Only return current templates

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Aug 7, 2026

TDQS

A3.6/5.0

Behavior2/5

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

With no annotations provided, the description must carry the disclosure burden. It only states 'List all available action templates' without mentioning the return format, the default current_only=true filter (which ironically may conflict with 'all'), or any prerequisites or side effects. This leaves significant behavioral ambiguity.

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?

The description is a single five-word sentence, perfectly front-loaded and free of any filler or redundant information.

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 list operation with an output schema and fully documented parameters, the description is mostly sufficient. It lacks mention of filtering behavior and differentiation from get_action_template, but the schema and tool name compensate for these gaps.

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 already provides complete descriptions and defaults for both keyword and current_only parameters (100% coverage), so the description adds no extra value. Baseline 3 applies because the schema fully handles parameter meaning.

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 uses the specific verb 'List' and identifies the resource 'action templates', clearly distinguishing it from the sibling get_action_template by indicating it returns all templates rather than a single one.

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?

Usage is implied by the verb 'List' but the description provides no explicit guidance on when to use this tool versus alternatives like get_action_template. No exclusions or context for selection are given.

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