Skip to main content
Glama
singlestore-mcp-server

singlestore-mcp-server

by jonasliesas

sql_editor_execute

Destructive

Execute a user-confirmed SQL statement, including writes and DDL, in the SQL Editor, returning streamed rows or the affected-row count.

Instructions

Run any single statement the user confirmed in the SQL Editor app (writes and DDL included).

Streamed like sql_editor_query: returns the first ``max_rows`` rows of a statement that returns rows (or
the affected-rows count) and the rest pages through sql_editor_rows; ``stream_id`` / Stop as there. The
statement is sent once (never retried after a dropped connection).

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

Input Schema

NameRequiredDescriptionDefault
sqlYes
tabNo
fileNo
tab_idNo
databaseNo
max_rowsNo
replacesNo
stream_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.11.0
    • addedInput schema / properties / replaces
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Replaces"
      +}
    • addedInput schema / properties / stream_id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Stream Id"
      +}
  2. Changed3 schema fields changedv0.9.0
    • addedInput schema / properties / file
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "File"
      +}
    • addedInput schema / properties / tab
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Tab"
      +}
    • addedInput schema / properties / tab_id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Tab Id"
      +}
  3. Addedv0.8.1

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so much of the safety profile is covered. The description still adds real value beyond them: the user-confirmation requirement, single-send/no-retry semantics after a dropped connection, and the affected-rows return shape for non-row statements. It omits transaction/commit behavior, which matters for a DDL-capable tool.

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?

Front-loaded with the key distinction and no filler, but the second paragraph is dense and uses terse shorthand ('``stream_id`` / Stop as there') plus doubled-backtick markup that reads as rendering noise rather than instruction.

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?

With no output schema and a destructive annotation, the description does the heavy lifting on return shape, streaming, and non-retry guarantees. It is not fully complete because five of eight parameters and the commit/transaction implications of executing DDL are never addressed.

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

Parameters4/5

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

Schema coverage is 0% with 8 parameters, yet the description explains sql (single statement), max_rows (first-N row cap), and stream_id (paging/Stop continuation). tab, file, tab_id, database, and especially replaces are left entirely undocumented, so it does not fully compensate for the coverage gap.

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?

Names a specific verb and resource ('Run any single statement') and immediately scopes it as the write/DDL-capable counterpart by contrasting with sql_editor_query. An agent can distinguish it from the read-oriented sibling 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 Guidelines4/5

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

Gives a clear precondition ('the user confirmed in the SQL Editor app') and routes continuation/paging to sql_editor_rows and Stop to sql_editor_stop. It never explicitly says when to prefer sql_editor_query instead of this tool, so the exclusion side is left implicit.

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

Deploy Server

Other Tools