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

every-db-mcp

by vmayfuture
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

db_get_table_structure

Retrieve columns, indexes, and constraints for a specific table by providing its name. Supports multiple database types.

Instructions

Get table structure (columns, indexes, constraints) for a specific table

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": {
      "tableName": "<tableName>"
    },
    "name": "db_get_table_structure"
  }
}

Input Schema

NameRequiredDescriptionDefault
databaseNoDatabase ID (default: mysql-dev)
tableNameYesName of the table

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations exist, so the description must disclose behavioral traits. It only states the action without indicating safety (e.g., read-only), permissions needed, or side effects, which is insufficient.

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?

Single sentence with no wasted words, front-loaded with key information. Perfect conciseness for the required content.

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

Completeness3/5

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

Despite having only 2 parameters, the description lacks details about the return format or behavior. Given no output schema, more completeness would be beneficial but not critical for this simple tool.

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?

Both parameters have schema descriptions, so schema coverage is 100%. The tool description adds minimal extra meaning beyond what the schema provides (e.g., default database mentioned only in schema). Baseline 3 is appropriate.

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 retrieves table structure including columns, indexes, and constraints, which is specific and distinguishes it from sibling tools like db_query or db_list_databases.

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?

No guidance on when to use this tool vs alternatives such as db_query. The description does not mention prerequisites or context, leaving the agent without decision support.

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