Skip to main content
Glama
singlestore-mcp-server

singlestore-mcp-server

by jonasliesas

Alerts

alerts
Read-only

Open a view of server-raised SingleStore cluster issues—long or failed queries, pipeline errors, node memory/disk thresholds, and offline nodes—with rules to edit and acknowledge or clear.

Instructions

Open the Alerts view: alerts the server raised while watching the SingleStore cluster in the background (queries running too long, slow or failed queries, failed pipeline batches / pipeline errors, node memory and disk thresholds, nodes not online, disk / memory projected full from the History trend), with the rules to edit and acknowledge / clear buttons.

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.8.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations supply readOnlyHint=true, and the description adds meaningful context beyond that: it explains the alerts originate from background monitoring of the SingleStore cluster, lists the concrete conditions that raise them, and discloses that the result carries a browser_url to be rendered as a link. What it omits is that the edit/acknowledge/clear buttons imply follow-up mutation tools, which the description does not name.

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 in the opening clause and the actionable output instruction (browser_url) comes last, which is a sensible order. The long parenthetical list of alert triggers is dense but each item is informative; it could be trimmed slightly without losing clarity.

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 correctly compensates by explaining that the result contains browser_url and how to present it. For a zero-parameter view opener with a readOnly annotation, this covers what an agent needs; only the relationship to the acknowledge/clear/update siblings is left implicit.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate beyond the schema; the baseline for a parameterless schema applies. No parameter-level meaning is needed or added.

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 — 'Open the Alerts view' — and enumerates the alert categories surfaced (long-running queries, failed pipeline batches, node memory/disk thresholds, projected capacity). An agent can tell this is the UI-launcher for alerts rather than a data query. It does not name the closely related siblings (alerts_data, alerts_badge, alerts_check_now) to differentiate, which keeps it below a 5.

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 — 'Open the Alerts view' plus the instruction to post browser_url under the app makes the UI-rendering intent clear. However, there is no explicit guidance on when to choose this over alerts_data (raw data) or alerts_badge (count), and no mention that acknowledging or clearing is done through alerts_ack / alerts_clear despite referencing those buttons.

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