Skip to main content
Glama
us-all

openmetadata-mcp-server

by us-all

create-database-service

Create a database service connector by providing name, database type, and connection configuration.

Instructions

Create a new database service connector

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesService name
serviceTypeYesDatabase type (e.g. 'Mysql', 'Postgres', 'BigQuery', 'Snowflake', 'Redshift', 'Hive', 'Mssql', 'Oracle')
connectionYesConnection configuration
descriptionNo

Implementation Reference

  • Zod schema for create-database-service tool: defines name, serviceType, connection (record), and optional description.
    export const createDatabaseServiceSchema = z.object({
      name: z.string().describe("Service name"),
      serviceType: z.string().describe("Database type (e.g. 'Mysql', 'Postgres', 'BigQuery', 'Snowflake', 'Redshift', 'Hive', 'Mssql', 'Oracle')"),
      connection: z.record(z.string(), z.any()).describe("Connection configuration"),
      description: z.string().optional(),
    });
  • Handler function for create-database-service: asserts write allowed, then POSTs to /services/databaseServices with params.
    export async function createDatabaseService(params: z.infer<typeof createDatabaseServiceSchema>) {
      assertWriteAllowed();
      return omClient.post("/services/databaseServices", params);
    }
  • src/index.ts:214-214 (registration)
    Registration of the 'create-database-service' tool with its schema and wrapped handler.
    tool("create-database-service", "Create a new database service connector", createDatabaseServiceSchema.shape, wrapToolHandler(createDatabaseService));
Behavior2/5

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

With no annotations, the description bears full burden but only states a basic action. No disclosure of idempotency, authentication needs, or side effects beyond creation.

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

Conciseness5/5

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

Single sentence with no extraneous words; perfectly concise.

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?

Despite having 4 parameters including a nested object and no output schema, the description provides no details about response, connection format, or required context; very incomplete.

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

Parameters3/5

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

Schema coverage is 75% with three parameters described; the description adds no additional meaning beyond the schema, so baseline is appropriate.

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 clearly states the action and resource ('Create a new database service connector'), which distinguishes it from other create tools like 'create-database' by specifying 'service connector'.

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 'update-database-service' or other create tools; no context about prerequisites or exclusions.

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