Skip to main content
Glama
us-all

openmetadata-mcp-server

by us-all

get-database-by-name

Retrieve detailed database information by providing a fully qualified name. Optionally filter fields and include deleted or non-deleted databases.

Instructions

Get database details by fully qualified name

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fqnYesFully qualified name (e.g. 'service.database')
fieldsNo
includeNo

Implementation Reference

  • src/index.ts:187-187 (registration)
    Registration of the 'get-database-by-name' tool with MCP server using the schema and handler from databases.ts
    tool("get-database-by-name", "Get database details by fully qualified name", getDatabaseByNameSchema.shape, wrapToolHandler(getDatabaseByName));
  • Zod schema defining input parameters: fqn (fully qualified name), optional fields, optional include filter
    export const getDatabaseByNameSchema = z.object({
      fqn: z.string().describe("Fully qualified name (e.g. 'service.database')"),
      fields: z.string().optional(),
      include: z.enum(["non-deleted", "deleted", "all"]).optional(),
    });
  • Handler function that constructs and sends a GET request to /databases/name/{fqn} using the OpenMetadata API client
    export async function getDatabaseByName(params: z.infer<typeof getDatabaseByNameSchema>) {
      const { fqn, ...query } = params;
      return omClient.get(`/databases/name/${encodeURIComponent(fqn)}`, query);
    }
Behavior2/5

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

No annotations provided. The description lacks details on behavior such as return fields (all vs. selected), handling of missing databases, error conditions, or rate limits. The 'include' parameter implies filtering by deleted status but is not explained.

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?

The description is short (one sentence) but lacks detail. It is front-loaded with the key verb and resource, but the terseness reduces clarity. An added sentence on usage context would improve it without breaking conciseness.

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 the lack of output schema and minimal parameter descriptions, the tool definition is incomplete. The agent cannot deduce the full response structure, behavior for different parameter combinations, or error handling. More context is needed for reliable invocation.

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?

With only 33% schema description coverage, the description adds minimal value: it mentions 'fully qualified name' for the required parameter but provides no context for 'fields' or 'include' (e.g., what values are allowed, effect on results). The description fails to compensate for the schema's gaps.

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 fully qualified name' clearly states the action (Get) and resource (database details). It distinguishes from sibling tools like 'get-database' (likely by ID) and other get-by-name tools for different entities, making the purpose unambiguous.

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' or other get-by-name tools. The description does not specify context, prerequisites, or exclusions, leaving the agent without decision support.

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