Skip to main content
Glama
jonasliesas

singlestore-mcp-server

by jonasliesas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

SingleStore Workspace

sql_editor
Read-only

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

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 editor has tabs; `sql` goes into the active tab, below the user's
text (or into a new tab with new_tab=true).

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", "workload" or "connections".
    table: For view="schema": table to pre-select in `database`.
    new_tab: With `sql`: open it in a new editor tab instead of the active one.

Input Schema

NameRequiredDescriptionDefault
sqlNo
viewNosql
tableNo
new_tabNo
databaseNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.0
    • addedInput schema / properties / new_tab
      Added value: +{
+  "default": false,
+  "title": "New Tab",
+  "type": "boolean"
+}
  2. Addedv0.8.1

TDQS

A4.7/5.0
Behavior4/5

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

With readOnlyHint=true already covering safety, the description adds real context beyond annotations: it discloses that the result contains browser_url and instructs the agent to post it as a clickable link, that SQL is not run automatically, and how inbound chat questions are tagged and answered. It is not exhaustive about every view's behavior, but it clearly exceeds what the annotation conveys.

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 and routing decision before any detail, and every paragraph carries information (views, sibling routing, chat tagging, browser_url, Args). It is longer than strictly necessary – the rail enumeration and chat-panel paragraph could be tightened – but nothing is pure filler.

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 five-parameter tool with no output schema and no annotation beyond readOnlyHint, the description supplies purpose, siblings, prerequisites (SQL is not executed), parameter semantics, and the one return value worth acting on (browser_url). An agent has everything needed to call and present the result.

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 description coverage is 0%, so the Args block carries the full burden and does so thoroughly: database is flagged case-sensitive, sql is marked 'not run automatically', table is scoped to view="schema", new_tab's interaction with sql is explained, and the admissible view values are enumerated even though the schema declares no enum. Without this text four of five parameters would be ambiguous.

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 then enumerates exactly what the workspace contains (schema tree, editor, results pane, rail views). It is immediately distinguishable from siblings such as run_sql, query_grid and schema_explorer, which are named in the text.

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 when-to-use guidance ('when the user wants to write, edit or run SQL themselves, or wants the combined workspace') and names the alternatives with their selecting conditions ('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 a further concrete 'when' case.

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