NeoCoder Neo4j AI Workflow

switch_incarnation

Switch the server to a new incarnation type to alter its reasoning mode. Use this to adapt the AI workflow for different data or query contexts.

Instructions

Switch the server to a different incarnation.

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": {
      "incarnation_type": "<incarnation_type>"
    },
    "name": "switch_incarnation"
  }
}

Input Schema

Name	Required	Description	Default
`incarnation_type`	Yes	Type of incarnation to switch to

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Aug 7, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the action without revealing potential side effects, reversibility, authentication requirements, or whether the switch disrupts ongoing operations.

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, direct sentence with no redundant wording. It is front-loaded and appropriately sized for the tool's simplicity.

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?

Despite the output schema and simple parameter set, the description lacks essential context about the consequences of switching, when it should be invoked, and how it relates to the get/list incarnation tools. The description is too minimal for a state-changing operation.

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?

Schema coverage is 100% for the single parameter, so the baseline is 3. The description does not add additional meaning to 'incarnation_type', but the schema already provides a clear title and description, so no deduction is warranted.

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 a specific action ('Switch') on a specific resource ('server') to a different 'incarnation', which distinguishes it from sibling read-only tools like get_current_incarnation and list_incarnations. However, it does not elaborate on what an incarnation is or the implications of switching.

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?

No guidance is provided about when to use this tool versus alternatives such as get_current_incarnation or list_incarnations. There is no mention of prerequisites, side effects, or when not to use it, leaving the agent to infer usage solely from the name.

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