deploy_graph_productionPromote graph staging to production. Creates a separate production Neo4j instance with its own credentials and database. Requires paid plan.
| Name | Required | Description | Default |
|---|---|---|---|
| project_id | Yes | Project ID (UUID) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate this is a non-read-only, non-idempotent, non-destructive operation. The description adds valuable context beyond these hints by stating it 'Creates a separate production Neo4j instance with its own credentials and database' and 'Requires paid plan,' disclosing side effects and prerequisites.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loaded with the primary action, and each sentence provides necessary information without redundancy. It is concise and efficiently structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with one parameter and no output schema, the description covers the core behavior and prerequisites. It does not mention potential errors or the exact response format, but given the tool's simplicity and existing annotations, it is sufficiently complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% for the single parameter (project_id), so the schema already documents it. The description adds no additional parameter semantics, but the baseline of 3 is appropriate given the schema's completeness.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action: 'Promote graph staging to production' and elaborates with 'Creates a separate production Neo4j instance with its own credentials and database.' This distinguishes it from sibling tools like deploy_graph_staging and the generic deploy_production/deploy_staging by specifying graph-specific staging-to-production promotion.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage when a graph is in staging and needs to be promoted to production, providing clear context. It does not explicitly list alternatives or exclusions, but the phrase 'graph staging to production' and the requirement for a paid plan sufficiently guide the agent on when this tool is appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools are clearly differentiated by domain (project vs graph_project) and action (create, get, list, delete). The main ambiguity is get_project vs get_project_info, which both claim to return detailed project information. Otherwise tool boundaries are clear.
The server follows a strong verb_noun convention, with parallel naming for graph and non-graph tools (create_project/create_graph_project, deploy_staging/deploy_graph_staging). Minor deviations include bulk_create_graph_nodes and fulltext_search_graph, but patterns remain predictable.
48 tools is a heavy surface, even when accounting for the two parallel product domains (relational and graph). Many tools are near-duplicates across domains, and the count exceeds the 25-tool threshold that feels manageable. It would benefit from consolidation or sub-servers.
Both project types have full life-cycle coverage: create, schema management, deployment, rollback, and deletion, plus graph data operations including bulk, search, and traversal. Minor gaps exist, such as no update_graph_relationship and the redundant get_project/get_project_info pair, but agents can accomplish core workflows.