Skip to main content
Glama
us-all

openmetadata-mcp-server

by us-all

list-database-services

List database services or connectors from OpenMetadata, filtering by fields, limit, pagination, and deletion status.

Instructions

List database services (connectors)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsNoComma-separated fields to include
limitNo
beforeNo
afterNo
includeNonon-deleted

Implementation Reference

  • The handler function that executes the 'list-database-services' tool logic — makes a GET request to /services/databaseServices with the provided params.
    export async function listDatabaseServices(params: z.infer<typeof listDatabaseServicesSchema>) {
      return omClient.get("/services/databaseServices", params);
    }
  • The input schema (listParams) for listing database services: fields, limit, before, after, include.
    const listParams = 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(),
      include: z.enum(["non-deleted", "deleted", "all"]).optional().default("non-deleted"),
    });
  • src/index.ts:211-211 (registration)
    Registration of the 'list-database-services' tool with its schema and handler via the tool() function.
    tool("list-database-services", "List database services (connectors)", listDatabaseServicesSchema.shape, wrapToolHandler(listDatabaseServices));
  • The omClient helper used to make HTTP API calls (imported from ../client.js).
    import { omClient } from "../client.js";
    import { assertWriteAllowed } from "./utils.js";
Behavior1/5

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

With no annotations, the description carries full responsibility for behavioral disclosure. It fails to mention that the tool likely supports pagination (via 'limit', 'before', 'after'), filtering (via 'include'), or any side effects. The description provides zero behavioral context.

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 extremely concise (one sentence). While brevity is positive, it sacrifices necessary detail. It could be considered appropriately minimal for a simple list tool, but given the schema complexity, it is under-specified.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has 5 parameters, no output schema, and no annotations. The description fails to explain pagination, filtering, return format, or admin requirements. It is woefully incomplete for an agent to use effectively.

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 20% (only 'fields' has a description). The description does not explain any parameters or their roles. Despite low coverage, no compensatory detail is added, leaving agents to guess parameter semantics.

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 action (list) and the resource (database services) with a clarifying parenthetical '(connectors)'. It unambiguously identifies what the tool does and distinguishes it from create, get, update, and delete sibling tools.

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 'get-database-service' or 'get-database-service-by-name'. There is no mention of use cases, prerequisites, or conditions under which the tool is appropriate.

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