Skip to main content
Search and list database objects (schemas, tables, columns, procedures, indexes) with pattern matching. This unified tool supports both targeted searches and browsing all objects, implementing progressive disclosure to minimize token usage.

​
Parameters

  • object_type (required): Type of object to search - "schema", "table", "column", "procedure", or "index"
  • pattern (optional): Search pattern using SQL LIKE syntax (% for wildcard, _ for single character). Defaults to "%" (match all)
  • schema (optional): Filter results to a specific schema
  • detail_level (optional): Level of detail - "names" (default), "summary", or "full"
  • limit (optional): Maximum results to return (default: 100, max: 1000)

​
Detail Levels

{
  "object_type": "table",
  "pattern": "user%",
  "detail_level": "names"
}

// Returns:
{
  "count": 3,
  "results": [
    { "name": "users", "schema": "public" },
    { "name": "user_profiles", "schema": "public" },
    { "name": "user_sessions", "schema": "public" }
  ]
}

​
Examples

{
  "object_type": "table",
  "pattern": "user%",
  "detail_level": "names",
  "limit": 10
}

​
Pattern Syntax

Use SQL LIKE pattern syntax for flexible matching:
  • % - Matches any sequence of characters
  • _ - Matches exactly one character
  • Case-insensitive matching
Examples:
  • user% → Matches “users”, “user_profiles”, “user_sessions”
  • %_id → Matches “user_id”, “order_id”, “product_id”
  • test_ → Matches “test_1”, “test_a” (but not “test_10”)
  • %user% → Matches “users”, “user_profiles”, “app_users”

​
Token Efficiency

This tool can reduce token usage by 90-99% compared to listing all objects:
ScenarioTraditional ApproachSearch ApproachToken Savings
Find “users” table in 500 tablesList all (full)Search (names)99%
Explore table structureList all tables firstSearch + drill down95%
Find ID columnsLoad all schemasSearch columns85%
Always start with detail_level: "names" and only request "summary" or "full" when you need additional information. This minimizes token usage while exploring the database.

​
Table and Column Comments

When using detail_level: "summary" or "full", the tool includes database comments/descriptions if they exist. This helps LLMs understand the purpose of tables and columns, especially in complex or legacy databases.
  • Table comments appear as the comment field on table results (summary and full levels)
  • Column descriptions appear as the description field on each column (full level only)
  • Fields are omitted when no comment is set, keeping responses token-efficient
DatabaseTable CommentsColumn Comments
PostgreSQLCOMMENT ON TABLECOMMENT ON COLUMN
MySQLALTER TABLE ... COMMENTALTER TABLE ... MODIFY COLUMN ... COMMENT
MariaDBALTER TABLE ... COMMENTALTER TABLE ... MODIFY COLUMN ... COMMENT
SQL Serversp_addextendedproperty (MS_Description)sp_addextendedproperty (MS_Description)
SQLiteNot supportedNot supported

​
Usage Patterns

// Find specific tables by pattern
{
  "object_type": "table",
  "pattern": "user%",
  "detail_level": "names"
}
Pattern defaults to "%" - You can omit the pattern parameter entirely to list all objects of the specified type. This unified tool replaces both search and list operations with a single, consistent interface.
The tool supports all three detail levels (names, summary, full) and works seamlessly with multi-database configurations. Results are limited by the limit parameter (default: 100, max: 1000) to prevent excessive token usage.