Skip to main content
Glama
us-all

openmetadata-mcp-server

by us-all

list-tables

List database tables with pagination, filter by database or schema, expand columns, owners, tags, and extract specific fields using dotted paths.

Instructions

List tables with pagination and optional field expansion

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsNoFields to include (e.g. 'columns,owners,tags,joins')
limitNoNumber of results per page
beforeNoCursor for backward pagination
afterNoCursor for forward pagination
databaseNoFilter by database FQN
databaseSchemaNoFilter by database schema FQN
includeNoInclude deleted entitiesnon-deleted
extractFieldsNoComma-separated dotted paths to project from response (e.g. 'id,name,owner.name,columns.*.name'). Use `*` as wildcard for arrays/objects. Wrap field names with dots in backticks. Reduces response tokens dramatically on large entities.

Implementation Reference

  • The handler function for list-tables. Makes a GET request to /tables with query params (pagination, filters) and applies field extraction.
    export async function listTables(params: z.infer<typeof listTablesSchema>) {
      const { extractFields, ...query } = params;
      const data = await omClient.get("/tables", query);
      return applyExtractFields(data, extractFields);
    }
  • Zod schema defining input parameters for list-tables: fields, limit, before/after cursors, database/schema filters, include deleted, extractFields.
    export const listTablesSchema = z.object({
      fields: z.string().optional().describe("Fields to include (e.g. 'columns,owners,tags,joins')"),
      limit: z.coerce.number().optional().default(10).describe("Number of results per page"),
      before: z.string().optional().describe("Cursor for backward pagination"),
      after: z.string().optional().describe("Cursor for forward pagination"),
      database: z.string().optional().describe("Filter by database FQN"),
      databaseSchema: z.string().optional().describe("Filter by database schema FQN"),
      include: z.enum(["non-deleted", "deleted", "all"]).optional().default("non-deleted").describe("Include deleted entities"),
      extractFields: z.string().optional().describe(extractFieldsDescription),
    });
  • src/index.ts:176-176 (registration)
    Registers the list-tables tool with the MCP server, linking the name, description, schema, and handler.
    tool("list-tables", "List tables with pagination and optional field expansion", listTablesSchema.shape, wrapToolHandler(listTables));
Behavior2/5

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

With no annotations, the description carries full burden for behavioral traits but only mentions pagination and field expansion. Missing details like read-only nature, authentication requirements, or rate limits.

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?

Single sentence, no waste. Could improve by adding more context without sacrificing brevity.

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?

No output schema, 8 parameters, but description is minimal. Lacks information about pagination mechanics, filtering behavior, and return format for a tool with significant complexity.

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 coverage is 100%, so parameters are well-documented. The description adds little beyond the schema, only hinting at pagination and field expansion. 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?

Description clearly states the action (list) and resource (tables), and mentions key features (pagination, field expansion). However, it does not differentiate from sibling list-* tools, which all follow a similar pattern.

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 like search-metadata or suggest-metadata. Lacks prerequisites or conditions for use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/us-all/openmetadata-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server