Skip to main content
Glama
singlestore-mcp-server

singlestore-mcp-server

by jonasliesas

restart_server

Idempotent

Reload the SingleStore MCP server to apply code or app changes without reconnecting; open apps and browser tabs reconnect automatically.

Instructions

Restart the SingleStore MCP server so code and app changes load, without reconnecting.

Open apps keep working after a reload of the app; open browser tabs and browser links reconnect to the new server by themselves.

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": "restart_server"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.8.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare not-readOnly, idempotent, non-destructive; the description adds genuinely new behavior: connected apps keep working and browser tabs/links auto-reconnect to the new instance. It still omits in-flight query handling and expected downtime window, which an agent restarting a server would want to know.

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?

Two short sentences, front-loaded with the action and its purpose. The second sentence partly restates "without reconnecting" in the form of "open apps keep working", which is mild but not damaging redundancy.

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 zero-parameter operation with an output schema and annotations covering the safety profile, the description supplies what structured data cannot: the reason to invoke it and the client-facing effects. Only downtime and in-flight work behavior remain unspecified.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate. Baseline applies and nothing in the text misleads about inputs.

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?

The description leads with a specific verb and resource ("Restart the SingleStore MCP server") and immediately states the reason ("so code and app changes load"). No sibling in the list performs a server restart, so there is nothing to confuse it with.

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?

It gives a clear trigger condition (after changing code or app assets that need to take effect) and implicitly removes the worry about losing state ("without reconnecting"). It stops short of explicit when-not guidance or naming any alternative recovery path, so it is strong context rather than a full decision rule.

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