Skip to main content
Glama
Sign In
sql-query-mcp

sql-query-mcp

by andyWang1688
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_databases

List all visible databases for a MySQL or Hive connection to identify available data sources.

Instructions

List visible databases for a MySQL or Hive connection.

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": {
      "connection_id": "<connection_id>"
    },
    "name": "list_databases"
  }
}

Input Schema

NameRequiredDescriptionDefault
connection_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0
  2. Removedv0.1.2
  3. First observedv0.1.3

TDQS

B3.2/5.0
Behavior2/5

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

Without annotations, the description carries full burden for behavioral disclosure. It only says 'list visible databases,' but does not mention whether it is read-only, auth requirements, or any side effects. This is minimal and insufficient for an agent to assess safety.

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 description is a single concise sentence (8 words) that is front-loaded with the action. However, it might be overly terse, missing details that could be included without harming conciseness.

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 no output schema and no annotations, the description should provide more context about inputs, outputs, and behavior. It lacks details on return format, prerequisites, or the concept of 'visible.' This is insufficient for complete understanding.

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

Parameters2/5

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

Schema coverage is 0%, so description must compensate. The description mentions 'for a MySQL or Hive connection,' adding context that connection_id refers to such a connection, but does not explain the parameter's meaning, format, or where to obtain it. This adds minimal value.

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 clearly states that the tool lists visible databases for a MySQL or Hive connection, giving a specific verb and resource. It implicitly differentiates from sibling tools like list_schemas or list_tables, which operate at different levels.

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?

The description implies the tool should be used when you need to see databases for a specific connection, but it lacks explicit guidance on when not to use it or alternatives. No mention of prerequisites or comparison with siblings.

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