Skip to main content
Glama
us-all

openmetadata-mcp-server

by us-all

get-schema

Retrieve database schema details by providing a schema UUID. Supports filtering by fields and inclusion of deleted schemas.

Instructions

Get database schema details by UUID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesDatabase schema UUID
fieldsNo
includeNo

Implementation Reference

  • src/index.ts:195-195 (registration)
    Registration of the 'get-schema' tool in the MCP server, using getSchemaSchema for validation and wrapping the getSchema handler.
    tool("get-schema", "Get database schema details by UUID", getSchemaSchema.shape, wrapToolHandler(getSchema));
  • Zod schema defining input validation for get-schema: requires 'id' (UUID), optional 'fields' and 'include'.
    export const getSchemaSchema = z.object({
      id: z.string().describe("Database schema UUID"),
      fields: z.string().optional(),
      include: z.enum(["non-deleted", "deleted", "all"]).optional(),
    });
  • Handler function for get-schema: extracts 'id' from params and makes a GET request to /databaseSchemas/{id} with remaining query parameters.
    export async function getSchema(params: z.infer<typeof getSchemaSchema>) {
      const { id, ...query } = params;
      return omClient.get(`/databaseSchemas/${id}`, query);
    }
Behavior2/5

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

No annotations provided, and the description does not disclose behavioral traits like idempotency, safety, authentication needs, or side effects. The description fails to compensate for the lack of annotations.

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?

The description is a single efficient sentence. However, it could add more detail without losing conciseness, such as clarifying what 'details' include.

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?

With 3 parameters, no output schema, no annotations, and minimal description, the tool lacks sufficient context for correct invocation. Unclear what 'details' are returned and how parameters work together.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33% (only 'id' described). The description adds no meaning to 'fields' or 'include' parameters, and does not compensate for low schema coverage.

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 clearly states the verb 'Get', the resource 'database schema details', and the identifier method 'by UUID'. This distinguishes it from sibling tools like 'get-schema-by-name'.

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 versus alternatives such as 'get-schema-by-name' or other sibling tools. Lacks context for appropriate usage.

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