Skip to main content
Glama
us-all

openmetadata-mcp-server

by us-all

get-database

Retrieve detailed metadata for a database using its UUID. Access specific fields and control inclusion of deleted entries.

Instructions

Get database details by UUID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesDatabase UUID
fieldsNo
includeNo

Implementation Reference

  • Input schema for the 'get-database' tool: accepts a 'id' (UUID string), optional 'fields', and optional 'include' enum.
    export const getDatabaseSchema = z.object({
      id: z.string().describe("Database UUID"),
      fields: z.string().optional(),
      include: z.enum(["non-deleted", "deleted", "all"]).optional(),
    });
  • Handler function that extracts 'id' from params and calls omClient.get() with the remaining query params to fetch a database by UUID.
    export async function getDatabase(params: z.infer<typeof getDatabaseSchema>) {
      const { id, ...query } = params;
      return omClient.get(`/databases/${id}`, query);
    }
  • src/index.ts:186-186 (registration)
    Registration of the 'get-database' tool on the MCP server with its schema and handler wrapped in error handling.
    tool("get-database", "Get database details by UUID", getDatabaseSchema.shape, wrapToolHandler(getDatabase));
  • Import statement bringing getDatabaseSchema and getDatabase from the tools/databases module into the registration file.
    import {
      listDatabasesSchema, listDatabases, getDatabaseSchema, getDatabase,
      getDatabaseByNameSchema, getDatabaseByName, createDatabaseSchema, createDatabase,
      updateDatabaseSchema, updateDatabase, deleteDatabaseSchema, deleteDatabase,
    } from "./tools/databases.js";
Behavior2/5

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

With no annotations, the description carries full burden but only says 'details'. Does not disclose whether deleted databases are returned by default, permission needs, or error cases. The 'include' parameter is not mentioned despite its filtering role.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely brief but at the cost of completeness. Every sentence should add value; this single sentence is too sparse to be maximally useful.

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, so description should hint at what is returned. Also lacks usage context among many sibling get tools. Incomplete for effective tool selection.

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 coverage is only 33% (id described). Description adds nothing about optional parameters 'fields' and 'include', leaving the agent to guess their purpose.

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 database details by UUID' clearly states the action (get), resource (database), and identifier (UUID), distinguishing it from siblings like get-database-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 like get-database-by-name. The agent is left unaware of the trade-offs between lookup methods.

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