Skip to main content
Glama
singlestore-mcp-server

singlestore-mcp-server

by jonasliesas

SingleStore Notebook

notebook
Read-only

Open a SingleStore SQL/Python workspace to run SQL cells, convert results to pandas DataFrames, and analyze with pandas, matplotlib, and a live connection; returns a browser URL.

Instructions

Open a SingleStore notebook: SQL and Python cells on a Jupyter kernel.

SQL cell results become pandas DataFrames for the Python cells; Python has
pandas, matplotlib and `conn` (a SingleStore connection). Notebooks are
.ipynb files in the user's SQL folder. It's also the Notebook view of the
SingleStore Workspace (sql_editor with view="notebook").

The result includes ``browser_url``: post it as a clickable link under the app.

Args:
    name: Notebook file to open (e.g. "sales.ipynb", or a SAS Viya ref "sas-content://<connection>/<path>");
        omit for a new notebook.
    database: Database for SQL cells (case-sensitive).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "notebook"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
databaseNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.8.1

TDQS

A4/5.0
Behavior4/5

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

With readOnlyHint=true, the annotations already establish that this is a safe read operation. The description adds substantial behavioral context beyond that: SQL cells produce pandas DataFrames, Python cells have pandas/matplotlib/conn, notebooks live in the SQL folder, and the result includes browser_url. It does not clarify permissions or whether omitting name creates a persisted file, which keeps it from a 5.

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?

The description is front-loaded with the core purpose, then adds environment details, file location, equivalences, return behavior, and argument notes. Most sentences are useful, though the instruction to post browser_url as a clickable link is app-specific and slightly detracts from a tight tool definition.

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?

For a two-optional-parameter tool with no output schema, the description is fairly complete: it covers the notebook environment, parameter semantics, file location, UI equivalence, and the returned browser_url. It leaves some gaps around sibling selection and whether a new notebook is persisted or merely opened unsaved.

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 parameter meaning, and it does. It explains that name can be a notebook filename or a SAS Viya reference and that omitting it starts a new notebook, and it states that database is case-sensitive and used for SQL cells.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource: "Open a SingleStore notebook," and explains what the notebook contains. It also identifies the equivalent Notebook view of the SingleStore Workspace via sql_editor, but it does not distinguish this tool from the sibling notebook_open, leaving some ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The description implies when to use it by saying it opens a notebook and is equivalent to sql_editor with view="notebook". However, it does not give explicit routing guidance versus notebook_open, notebook_run, notebook_save, or the sql_editor tools, so the agent must infer the appropriate choice.

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