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

mcp-multi-db

by mahAnuj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

describe_table

Retrieve column definitions for a table in a configured PostgreSQL, MySQL, or SQLite database to inspect its structure and schema.

Instructions

Describe columns for a table in a configured database.

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": {
      "database_id": "<database_id>",
      "table": "<table>"
    },
    "name": "describe_table"
  }
}

Input Schema

NameRequiredDescriptionDefault
tableYesTable name
schemaNoSchema name (Postgres/MySQL). Ignored for SQLite.
database_idYesDatabase id from list_databases

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.1
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.0.2

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it never states that this is a read-only metadata operation, what happens if the table does not exist, or whether it covers indexes/constraints in addition to columns. The phrase "configured database" hints at a pre-registered connection but does not explain access or failure behavior.

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?

A single sentence with no filler, and the resource and scope are front-loaded. There is no redundancy or tangents to trim.

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?

With no annotations and no output schema, the description should explain what "describe" actually returns (column names, types, nullability, defaults) since nothing else does. For a schema-introspection tool whose output is the whole point, that omission leaves a meaningful gap.

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 description coverage is 100%, with each of the three parameters already documented, including the SQLite caveat for schema. The description adds nothing beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Describe columns for a table" states a specific verb (describe) and resource (a table's columns), which is clearly distinguishable from list_databases, list_tables, and run_query by the object it operates on. It stops short of explicitly contrasting itself with the sibling metadata tools, so it is clear but not fully differentiated.

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 gives no when-to-use guidance, no prerequisites (such as needing a database_id from list_databases first), and no indication of when an agent should prefer list_tables or run_query instead. Usage is only inferable from the tool name.

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