Skip to main content
Glama
jonasliesas

singlestore-mcp-server

by jonasliesas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Query Results Grid

query_grid
Read-only

Run read-only SQL and open results in an interactive grid to browse, sort, filter, or export CSV, with editable query re-runs.

Instructions

Run a read-only SQL query and show the results in an interactive grid.

Use this when the user wants to see, browse, sort, filter or export
(CSV) query results, or when a result is too large to read as text. The
user can also edit and re-run the query from the grid. You receive only
a summary with the first 20 rows; the user sees all fetched rows.

Only read-only statements are accepted: SELECT, WITH, SHOW, DESCRIBE,
DESC, EXPLAIN (one statement, no SELECT ... INTO). For writes, DDL or when
you just need a value for your own reasoning, use run_sql instead.

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:
    sql: A single read-only statement.
    database: Database to run it against (defaults to the connection's
        configured database).
    max_rows: Maximum rows to fetch, 1-10000 (default 1000). The result
        is flagged as truncated when more rows exist.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sqlYes
databaseNo
max_rowsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A4.6/5.0
Behavior5/5

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

Adds substantial behavior beyond the readOnlyHint annotation: the exact accepted statement types (SELECT/WITH/SHOW/DESCRIBE/DESC/EXPLAIN), the single-statement and no SELECT...INTO constraints, the fact that the agent receives only a 20-row summary while the user sees all rows, and the browser_url return value. These are consequential traits an agent could not derive from annotations alone.

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 purpose, then usage, then constraints, then args in a clean block; nearly every sentence earns its place. It runs slightly long, and the grid-editing aside ('user can also edit and re-run the query') is ancillary to the agent's task.

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, the description still explains the return shape (summary, first 20 rows, browser_url, truncation flag), which is strong. The one meaningful gap is not explaining how the agent obtains the full result set (e.g., via query_grid_rows), which matters given the deliberate 20-row cap.

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 description must carry the burden, and it does: sql is documented as a single read-only statement, database as defaulting to the connection's configured database, and max_rows with its valid range (1-10000), default (1000), and truncation-flag behavior. All three parameters gain meaning beyond the bare schema titles.

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+resource ('Run a read-only SQL query and show the results in an interactive grid') and differentiates itself from the read-text sibling run_sql. An agent can identify the tool's role without opening the 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 explicit when-to-use conditions (browse/sort/filter/export results, or results too large to read as text) and a when-not with a named alternative (writes, DDL, or when you just need a value -> run_sql). It does not mention the closely-related query_grid_rows sibling, which is presumably the way to fetch beyond the summarized rows, leaving that routing to inference.

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