Skip to main content
Glama
jonasliesas

singlestore-mcp-server

by jonasliesas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

SingleStore Workspace

sql_editor
Read-only

Open an interactive SQL workspace for SingleStore to write, edit, and run queries, explore schemas, and monitor pipelines or clusters.

Instructions

Open the SingleStore workspace: an interactive SQL editor plus views.

A slim rail on the left switches between the SQL Editor (schema tree,
editor with autocomplete for keywords, SingleStore functions, databases,
tables and columns, and a results pane), the Schema Explorer, the Pipeline
Monitor and the Cluster Monitor. Use this when the user wants to write,
edit or run SQL themselves, or wants the combined workspace. To run a
query for your own reasoning use run_sql; to show results use query_grid.
The editor has a chat panel: questions from it arrive in the conversation
tagged "[SQL Editor <id>]"; answer those with sql_editor_reply.

The result includes ``browser_url``, which opens this view full-window in
the user's browser: post it as a clickable link right under the app.

Args:
    database: Database to start in (case-sensitive).
    sql: SQL to put in the editor (not run automatically).
    view: View to show first: "sql" (default), "notebook", "schema", "pipelines", "cluster", "history" (Query History), "alerts" or "connections".
    table: For view="schema": table to pre-select in `database`.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sqlNo
viewNosql
tableNo
databaseNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.8.1

TDQS

A4.7/5.0
Behavior4/5

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

Annotations only supply readOnlyHint=true, which is consistent with opening a UI view. The description adds genuinely non-obvious behavior: the embedded chat panel delivers messages tagged '[SQL Editor <id>]' that must be answered with sql_editor_reply, and the result carries a browser_url that should be posted as a clickable link. It stops short of disclosing session/auth or lifecycle behavior, but this is well beyond what the annotation provides.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose, then scope, routing, behavioral quirks and args in a logical order. Every sentence carries information, though the rail-navigation enumeration is slightly verbose for an agent that mainly needs the routing and arg details.

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?

With no output schema, the description compensates by describing the return shape ('The result includes browser_url') and the required follow-up action. Combined with full parameter documentation, the view enum, and the sibling routing rules, an agent has everything needed to invoke and post-process this tool correctly.

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

Parameters5/5

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

Schema coverage is 0% and no enums are declared, so the description carries the entire burden, and it delivers: it enumerates all eight valid values for view (sql, notebook, schema, pipelines, cluster, history, alerts, connections), documents the table argument as conditional on view='schema', notes database is case-sensitive, and warns that sql is not run automatically.

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 ('Open the SingleStore workspace: an interactive SQL editor plus views') and immediately enumerates what the workspace contains (Schema Explorer, Pipeline Monitor, Cluster Monitor). It distinguishes itself from the closest siblings by naming run_sql and query_grid and giving the condition that selects each.

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?

Explicit selection criteria: 'Use this when the user wants to write, edit or run SQL themselves, or wants the combined workspace,' followed by explicit routing rules ('to run a query for your own reasoning use run_sql; to show results use query_grid'). The chat-panel routing to sql_editor_reply is also spelled out, so both the when and the when-not are covered.

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