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

every-db-mcp

by vmayfuture
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

db_execute

Execute INSERT, UPDATE, DELETE, and DDL statements on MySQL, GaussDB, Oracle, and DM8 databases. Respects per-database permissions.

Instructions

Execute INSERT/UPDATE/DELETE/DDL operations against configured databases. Respects per-database permissions.

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_execute"
  }
}

Input Schema

NameRequiredDescriptionDefault
sqlYesThe SQL statement to execute (INSERT/UPDATE/DELETE/DDL)
databaseNoDatabase ID to execute against (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

B3.4/5.0
Behavior2/5

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

No annotations provided, so description must fully disclose behavior. It mentions permission respect but lacks details on error handling, transaction behavior, commit semantics, or return format. Insufficient for a mutation 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?

Two concise, front-loaded sentences with no redundant information. Every sentence serves a purpose.

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?

For a potentially dangerous SQL execution tool, description is too minimal. Missing information on transactions, error handling, multiple statements, and no output schema. Requires supplementation.

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?

Schema coverage is 100% and parameter descriptions are adequate. Tool description adds marginal value beyond schema, not compensating for missing behavioral context.

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?

Description clearly states verb 'Execute' and resource 'INSERT/UPDATE/DELETE/DDL operations against configured databases', distinguishing it from siblings like db_query (SELECT) and db_get_table_structure (schema).

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?

Implies use for mutation/DDL operations but no explicit guidance on when to use vs db_query or alternatives. No exclusions or prerequisites mentioned.

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