Skip to main content
Glama
Sign In
mysql-mcp-server

mysql-mcp-server

by eeantoss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

database_list_sessions

List active database sessions to monitor connections and troubleshoot problems. Works through the MySQL MCP server, eliminating the need for a local MySQL client.

Instructions

List active database sessions

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations provided, the description must carry full responsibility for disclosing behavior. It only says 'List active database sessions' without mentioning whether this is a read-only operation, whether it requires an existing connection, how 'active' is defined, or any potential side effects. This is minimal and lacks transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, clear sentence that immediately conveys the purpose. It is concise and well-structured, with no unnecessary words or repetition.

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?

Given the tool is simple (no parameters), the description is relatively complete for a basic list operation. However, there is no output schema, and the description does not explain what information is returned for each session, what 'active' means, or any operational requirements. This leaves gaps for an agent to correctly interpret the tool's behavior.

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 has zero parameters, and the schema is empty. Per the rubric, a baseline of 4 is appropriate when there are no parameters. The description correctly matches this, adding no confusion about parameter usage.

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 exactly states the verb 'List' and the resource 'active database sessions', which clearly identifies what the tool does. It distinguishes itself from sibling tools like database_list_environments by focusing specifically on sessions.

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?

The description provides no guidance on when to use this tool versus alternatives, nor any context about prerequisites, side effects, or intended scenarios. For a simple list operation, usage is implied, but no explicit guidance is given.

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