Skip to main content
Glama
jonasliesas

singlestore-mcp-server

by jonasliesas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Config

cluster_config
Read-only

List SingleStore engine variables (configuration parameters) with their values per node, read-only.

Instructions

List SingleStore engine variables (configuration parameters) with their values per node, read-only.

Marks variables whose value differs from the documented default (defaults come from the docs page for the
cluster's version, downloaded once and kept locally) and variables whose value differs between nodes.
Opens the Config view; nothing is changed.

Args:
    search: Only variables whose name, description or category contains this text.
    changed_only: Only variables changed from the default or differing between nodes.

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchNo
changed_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.9.0

TDQS

A3.8/5.0
Behavior4/5

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

Beyond readOnlyHint=true, the description discloses useful behavior: defaults are fetched from the docs page for the cluster version and cached locally, variables differing from defaults or between nodes are marked, and the Config view is opened with nothing modified. It stops short of describing result shape beyond browser_url.

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?

Purpose and read-only guarantee are front-loaded, and the Args block is needed given the empty schema descriptions. The prose about downloading docs and posting a link under the app is slightly verbose but each element informs behavior.

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 usefully notes the result includes browser_url and how to present it. For a read-only two-param list tool the coverage is solid, though return format details (fields per variable, node grouping) are left implicit.

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 full burden and largely does so: 'search' matches name, description, or category, and 'changed_only' filters to values changed from default or differing between nodes. Minor gaps remain (e.g. match case sensitivity), so not a 5.

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: list SingleStore engine variables with values per node, and notes it is read-only. It is clear what the tool does, but it does not distinguish itself from the nearby sibling 'config_data' or explain how the two relate.

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?

Usage is implied rather than stated: an agent can infer you call it to inspect engine variables or to see what has drifted from defaults. There is no explicit when-to-use guidance or comparison against alternatives such as config_data or schema_explorer tools.

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