Skip to main content
Glama
us-all

openmetadata-mcp-server

by us-all

get-table

Retrieve detailed metadata for a specific table using its unique identifier.

Instructions

Get table details by UUID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTable UUID
fieldsNoOpenMetadata fields to include
includeNo
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

  • src/index.ts:177-177 (registration)
    Registration of the 'get-table' tool with its schema and handler via the tool() helper function.
    tool("get-table", "Get table details by UUID", getTableSchema.shape, wrapToolHandler(getTable));
  • Zod schema 'getTableSchema' defining input validation for get-table: id (UUID), fields, include, extractFields.
    export const getTableSchema = z.object({
      id: z.string().describe("Table UUID"),
      fields: z.string().optional().describe("OpenMetadata fields to include"),
      include: z.enum(["non-deleted", "deleted", "all"]).optional(),
      extractFields: z.string().optional().describe(extractFieldsDescription),
    });
  • Handler function 'getTable' that makes a GET request to /tables/{id} and applies extractFields with default fields.
    export async function getTable(params: z.infer<typeof getTableSchema>) {
      const { id, extractFields, ...query } = params;
      const data = await omClient.get(`/tables/${id}`, query);
      return applyExtractFields(data, extractFields ?? GET_TABLE_DEFAULT_FIELDS);
    }
  • Helper function 'applyExtractFields' used by the handler to process response field expansions.
    // Re-export from @us-all/mcp-toolkit for backward compatibility.
    // New code should import directly from "@us-all/mcp-toolkit".
    export { applyExtractFields, extractFieldsDescription } from "@us-all/mcp-toolkit";
  • Default fields constant used when no custom 'fields' or 'extractFields' param is provided.
    const GET_TABLE_DEFAULT_FIELDS = "id,name,fullyQualifiedName,description,columns,owners,tags,database";
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure, but it only states the action without mentioning read-only nature, side effects, or any constraints.

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?

The description is a single, efficient sentence that conveys the core purpose with no superfluous words.

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?

Given 4 parameters and no output schema, the description lacks details such as what fields are returned, how the 'include' parameter filters results, and the purpose of 'extractFields'. It is insufficient for a complete understanding.

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 75%, and the description adds no additional meaning beyond what the input schema provides. For example, the include and extractFields parameters have detailed schema descriptions, but the tool description does not elaborate on them.

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

Purpose5/5

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

The description 'Get table details by UUID' uses a specific verb ('Get') and resource ('table details') with a clear identifier ('UUID'), distinguishing it from siblings like get-table-by-name that use name instead.

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?

The description implies usage when UUID is known, but provides no explicit guidance on when to use this versus alternatives like get-table-by-name, and no exclusions or prerequisites.

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