Skip to main content
Glama
multidb-mcp

multidb-mcp

describe_table

Retrieve column metadata for a table, including column names, types, lengths, nullability, defaults, and comments.

Instructions

Return column metadata for a table: column name, type, length, nullability, default and comment.

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

Input Schema

NameRequiredDescriptionDefault
tableYesTable name.
schemaNoSchema the table lives in. Uses the connection default if omitted.
connectionNoConnection name. Omit when only one is configured.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the exact return payload, which strongly implies a read-only metadata operation, but it says nothing about permission requirements, behavior for a nonexistent table/schema, or whether the connection must already be established.

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, front-loading the action and immediately following with the concrete fields returned. Nothing could be removed without losing information.

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

Completeness4/5

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

For a simple read-only metadata tool with three fully documented parameters and no output schema, the enumeration of returned columns effectively substitutes for a return-value spec. It is close to complete; only error/edge-case behavior and sibling routing are unaddressed.

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% and each of the three parameters (table, schema, connection) is documented in the schema itself, including the default-connection fallback. The description adds no parameter-level detail beyond what the schema already provides, so the baseline of 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?

States a specific verb ('Return') and resource ('column metadata for a table') and enumerates the returned fields: name, type, length, nullability, default, comment. An agent can distinguish this from execute_sql or list_tables without further reading, though the description never explicitly contrasts itself with those siblings.

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?

Usage is only implied: the tool is clearly meant for inspecting a table's shape (e.g. before writing SQL). There is no explicit statement of when to prefer it over execute_sql with a DESCRIBE query, and no mention of prerequisites such as the table needing to exist on the active connection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.