mcp-server-rdbms

Overview Schema Source Related Servers Discussions Admin

schema_list_tables

List tables and views with comments in a database schema. Filter by wildcard pattern, route to a specific database alias, and optionally include foreign-key relationships.

Instructions

获取指定模式下的数据表/视图清单与表注释。支持多数据库路由（通过 db 参数指定连接别名，缺省时路由至默认库）；支持基于通配符（如 user_*）的 pattern 内存过滤；默认不加载外键以保障大库极速响应，显式指定 include_foreign_keys=True 时聚合全库外键拓扑。

Input Schema

TableJSON Schema

Name	Required	Description	Default
`db`	No
`schema`	No
`pattern`	No
`include_views`	No
`include_foreign_keys`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.4.0Oct 15, 2026

addedInput schema / properties / include_foreign_keys

Added value: +{
+  "default": false,
+  "title": "Include Foreign Keys",
+  "type": "boolean"
+}

addedInput schema / properties / pattern

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Pattern"
+}

First observedv1.1.4Oct 5, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations the description carries the full burden, and it does disclose meaningful behavior: the default skips foreign keys for speed on large databases, and include_foreign_keys=True triggers an expensive full-database FK topology aggregation. It omits read-only confirmation, permission requirements, and any result-size limits, keeping it out of the top tier.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first sentence, with the parameter behaviors following in compact semicolon-delimited clauses. No sentence is wasted, though the paragraph is dense and could be split for readability.

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?

An output schema exists, so return-value explanation is unnecessary, and the description covers routing, filtering, and FK behavior for a 5-parameter tool. It leaves the include_views toggle and any large-schema result limits unaddressed, which keeps it just short of complete.

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 0%, so the description must compensate, and it explains db (connection alias, default routing), pattern (wildcard in-memory filtering such as user_*), and include_foreign_keys (default off, enables FK aggregation); the schema-scoping intent is also conveyed. Only include_views receives no explanation, preventing a 5.

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?

The opening sentence gives a precise verb+resource: it lists tables/views and their comments for a given schema, which is naturally distinct from the single-table scope of schema_describe_table. It never explicitly names or contrasts with the siblings, so it stops short of a 5.

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 through parameter behavior (db routing, pattern filtering, FK toggle). There is no statement of when to prefer this over schema_describe_table or db_info, and no prerequisites or exclusions are given.

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

Deploy Server