Skip to main content
Glama
us-all

openmetadata-mcp-server

by us-all

list-schemas

List database schemas with pagination and filtering by fields, database, or inclusion status.

Instructions

List database schemas with pagination

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsNoComma-separated fields to include
limitNo
beforeNo
afterNo
databaseNoFilter by database FQN
includeNonon-deleted

Implementation Reference

  • The handler function for list-schemas that makes a GET request to /databaseSchemas with pagination and filtering params.
    export async function listSchemas(params: z.infer<typeof listSchemasSchema>) {
      return omClient.get("/databaseSchemas", params);
    }
  • Zod schema defining input parameters for list-schemas: fields, limit (default 10), before, after, database (FQN filter), include (default non-deleted).
    export const listSchemasSchema = z.object({
      fields: z.string().optional().describe("Comma-separated fields to include"),
      limit: z.coerce.number().optional().default(10),
      before: z.string().optional(),
      after: z.string().optional(),
      database: z.string().optional().describe("Filter by database FQN"),
      include: z.enum(["non-deleted", "deleted", "all"]).optional().default("non-deleted"),
    });
  • src/index.ts:194-194 (registration)
    Registration of the list-schemas tool on the MCP server with its schema and handler, under the 'core' category.
    tool("list-schemas", "List database schemas with pagination", listSchemasSchema.shape, wrapToolHandler(listSchemas));
Behavior2/5

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

With no annotations, the description carries the full burden but only states 'List database schemas with pagination'. It does not disclose read-only nature, side effects, security requirements, or how pagination behaves (e.g., cursor-based vs offset).

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, short sentence without filler. While concise, it sacrifices necessary detail for compactness.

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 6 parameters, no output schema, and no annotations, the description is inadequate. It does not explain filtering options, pagination mechanics, or the structure of returned data. A tool with this complexity requires more context.

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% (fields and database described). The description adds no new meaning beyond 'with pagination', leaving parameters like before, after, limit, and include unexplained. The enum for include is not clarified.

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 description 'List database schemas with pagination' clearly states the action (list) and resource (database schemas) with a feature (pagination). It is distinguishable from sibling tools like list-databases or list-tables, though it could be slightly more specific about what 'schemas' encompasses.

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 is provided on when to use this tool versus alternatives such as list-databases or list-tables. There is no mention of prerequisites, context, or when this tool should be avoided.

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