Skip to main content
Glama
singlestore-mcp-server

singlestore-mcp-server

by jonasliesas

sql_editor_ask

Read-only

Answers SQL Editor chat questions and sends responses to the editor inbox, using the chosen language, profile, and optional SAS context.

Instructions

Answer a SQL Editor chat question in the app; the reply arrives in the editor's inbox.

``profile`` picks speed vs depth: "fast", "balanced" (default) or "thorough". ``language``: what the tab runs
as (singlestore, procsql, fedsql, cas). For a SAS tab, ``sas`` is its context: ``library`` (library or caslib),
``library_info`` ({name, engine/type, database, singlestore, singlestore_kind}), ``tables`` (names, or
{name, loaded}), ``columns`` ({"LIB.TABLE": [{name, type, length, format}]}) and ``options``; the question then
carries the SAS guide of that language (once per Claude session and language).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "editor_id": "<editor_id>",
      "question": "<question>"
    },
    "name": "sql_editor_ask"
  }
}

Input Schema

NameRequiredDescriptionDefault
sasNo
sqlNo
profileNo
databaseNo
languageNosinglestore
questionYes
selectedNo
editor_idYes
last_resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.11.0
    • addedInput schema / properties / language
      Added value: +{
      +  "default": "singlestore",
      +  "title": "Language",
      +  "type": "string"
      +}
    • addedInput schema / properties / sas
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": true,
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Sas"
      +}
  2. Addedv0.8.1

TDQS

B3.1/5.0
Behavior3/5

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

With only readOnlyHint=true supplied, the description adds useful context: the reply is delivered asynchronously to the editor's inbox, profile defaults to balanced, and SAS context triggers injecting the SAS guide once per Claude session and language. It still omits auth requirements, whether the inbox write is a side effect, and how cancellation or retrieval works.

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 purpose is front-loaded, followed by parameter-specific details grouped by profile, language, and SAS context. It is dense for its length but generally earns its place; the SAS sentence is slightly awkward but not filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter tool with no schema descriptions, no output schema, and only readOnlyHint, the description covers core chat behavior and some SAS context but leaves most optional parameters unexplained. An agent can make a basic call, but not confidently understand the full parameter surface or retrieval workflow.

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

Parameters3/5

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

Schema coverage is 0% across 9 parameters, so the description must carry parameter meaning. It explains profile values, language values, and the nested SAS context fields in useful detail, but leaves sql, database, selected, editor_id, and last_result undefined.

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 states a specific verb and resource: "Answer a SQL Editor chat question in the app," and notes the reply arrives in the editor's inbox. It is clear what the tool does, but it does not distinguish this ask operation from sibling tools such as sql_editor_assistant, sql_editor_reply, or sql_editor_inbox.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool versus alternatives like sql_editor_assistant or notebook_ask, nor when not to use it. The profile tradeoff explains parameter tuning, not tool selection.

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