Skip to main content
Glama
Sign In
every-db-mcp

every-db-mcp

by vmayfuture
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

db_query

Execute SQL SELECT queries on MySQL, Oracle, GaussDB, and DM8 databases with configurable row limits and database selection.

Instructions

Execute SQL queries against configured databases (MySQL, DM8, Oracle, GaussDB).

Available databases:

  • mysql-dev (mysql): SELECT

  • gaussdb-dev (gaussdb): SELECT

  • oracle-dev (oracle): SELECT

  • dm8-dev (dm8): SELECT

Default database: mysql-dev

Use 'db_query' for SELECT queries, 'db_execute' for INSERT/UPDATE/DELETE/DDL operations.

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": {
      "sql": "<sql>"
    },
    "name": "db_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
sqlYesThe SQL SELECT query to execute
maxRowsNoMaximum number of rows to return (default: 100)
databaseNoDatabase ID to query (default: mysql-dev). Available: mysql-dev, gaussdb-dev, oracle-dev, dm8-dev

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations, the description carries full burden. It states the tool is for SELECT queries only (read-only), default database, and row limit. It does not mention auth or rate limits, but it's sufficient for a read-only query tool.

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?

Concise and well-structured with bullet points for databases, no fluff, key information front-loaded. Every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers all essential aspects: purpose, databases, parameter details, and sibling distinction. No output schema needed for a query tool; description is complete for user guidance.

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 coverage is 100% (baseline 3). Description adds value by listing default database, available databases for the 'database' parameter, clarifying 'sql' must be a SELECT query, and noting maxRows default.

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 the tool executes SQL SELECT queries against configured databases, and distinguishes it from db_execute. It lists specific database types, making the purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly specifies using db_query for SELECT queries and db_execute for mutations, and lists available databases. Provides clear guidance on when to use this tool vs alternatives.

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