Skip to main content
Glama
SynapCores MCP Server

SynapCores MCP Server

Official

Run a SQL write or schema change

execute
Destructive

Run INSERT, UPDATE, DELETE, or schema changes (CREATE, ALTER, DROP) on a SynapCores database, returning rows affected and execution time. Use dry_run=true to check syntax without modifying data.

Instructions

Run a SQL write (INSERT, UPDATE, DELETE) or schema change (CREATE, ALTER, DROP) against a SynapCores database and return rows_affected and execution_time_ms. Use query for SELECT/WITH, which this tool rejects, and validate_query or dry_run=true to check syntax without changing anything; Cypher statements sent here run on the graph, as with graph_query. Changes are permanent (DELETE and DROP remove data), and read-only API keys are refused.

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": {
      "sql": "<sql>"
    },
    "name": "execute"
  }
}

Input Schema

NameRequiredDescriptionDefault
sqlYesThe INSERT, UPDATE, DELETE, CREATE, ALTER or DROP statement to run.
dry_runNotrue = only check the syntax and change nothing (default false).
databaseNoDatabase name; omit to use the default database.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.0.1
    • changedInput schema / properties / database / description
      Previous value: -"Database name (optional)"New value: +"Database name; omit to use the default database."
    • changedInput schema / properties / dry_run / description
      Previous value: -"Validate without executing (default: false)"New value: +"true = only check the syntax and change nothing (default false)."
    • changedInput schema / properties / sql / description
      Previous value: -"SQL statement to execute"New value: +"The INSERT, UPDATE, DELETE, CREATE, ALTER or DROP statement to run."
  2. First observedv1.0.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description still adds substance beyond them: changes are permanent, DELETE/DROP remove data, read-only API keys are refused, and the response contains rows_affected and execution_time_ms. These are auth, irreversibility, and return-value details the annotations cannot convey.

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?

Two sentences, front-loaded with the operation and its accepted statement types, then alternatives and safety warnings. Every clause carries actionable information; nothing is padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, non-idempotent, open-world-free write tool with no output schema, the description covers accepted inputs, rejected inputs, escape hatches, permanence, auth constraints, and return fields. Nothing an agent needs to invoke it safely is missing.

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%, so all three parameters including dry_run and database are already documented. The description reinforces dry_run's meaning and links it to `validate_query`, but adds no new syntax or format detail beyond the schema, matching the baseline for high coverage.

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?

States a specific verb-and-resource pair and enumerates the exact statement classes it accepts (INSERT, UPDATE, DELETE, CREATE, ALTER, DROP) plus the target system. It explicitly names the boundary with `query`, so an agent can separate the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit routing rules: SELECT/WITH goes to `query` (this tool rejects it), syntax checking goes to `validate_query` or dry_run=true, and Cypher goes to `graph_query`. When-to-use, when-not-to-use, and alternatives are all present.

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