Skip to main content
Glama
jonasliesas

singlestore-mcp-server

by jonasliesas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Schema Explorer

schema_explorer
Read-only

Explore SingleStore cluster schemas interactively. View databases, tables, views, storage types, row counts, sizes, columns, keys, DDL, and data previews in a visual interface.

Instructions

Open an interactive Schema Explorer for the SingleStore cluster.

Shows every database and its tables/views with storage type
(columnstore/rowstore/reference), row counts and sizes; for a selected
table it shows columns, shard key and sort key, the full CREATE TABLE DDL
and a 50-row data preview. The user can browse freely and ask follow-up
questions from the UI. Use this when the user wants to explore, browse or
understand the schema visually. For a plain list of tables or columns
inside your own reasoning, list_tables / describe_table are cheaper.

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: Pre-select this database (case-sensitive). Omit to start at the database list.
    table: Pre-select this table or view in `database` (case-sensitive). Requires `database`.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tableNo
databaseNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds real behavioral context beyond that: it is interactive, the user can browse freely and ask follow-up questions, and it returns a browser_url meant to be posted as a clickable link. It does not mention pagination or size limits on the preview, but the UI-opening behavior is well disclosed.

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-loads the core purpose, then capabilities, then usage routing, then return-value handling, then args. Information-dense with minimal filler; the Args block is slightly repetitive of the prose but still earns its place as structured detail.

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?

Although there is no output schema, the description explains the key return artifact (browser_url) and how to present it. Combined with the full capability and parameter coverage, an agent has everything needed to select and invoke this tool correctly.

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 description coverage is 0%, so the description carries the load and does so: it explains that database pre-selects a database (case-sensitive) and that omitting it starts at the database list, and that table pre-selects within database and requires database. The cross-parameter dependency and case-sensitivity are both stated, though the failure behavior when table is given without database is left implicit.

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 an interactive Schema Explorer for the SingleStore cluster') and then enumerates exactly what it displays (databases, tables/views, storage type, row counts, shard/sort keys, DDL, preview). It distinguishes itself from the list-oriented siblings by framing itself as a visual browsing tool.

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 an explicit when-to-use ('when the user wants to explore, browse or understand the schema visually') and a when-not-to-use with named alternatives ('For a plain list of tables or columns inside your own reasoning, list_tables / describe_table are cheaper'). The routing decision is fully specified.

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