Skip to main content
Glama
us-all

openmetadata-mcp-server

by us-all

create-stored-procedure

Creates a new stored procedure in a specified database schema with optional code, tags, and ownership.

Instructions

Create a new stored procedure

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesStored Procedure name
databaseSchemaYesFQN of the parent database schema
descriptionNoStored Procedure description in markdown
storedProcedureCodeNoStored procedure code definition (e.g. {language:'SQL', code:'...'})
tagsNoTags to apply
ownersNoOwner references

Implementation Reference

  • The handler function that executes the 'create-stored-procedure' tool logic. It calls assertWriteAllowed() to check write permissions, then POSTs to '/storedProcedures' with the provided parameters.
    export async function createStoredProcedure(params: z.infer<typeof createStoredProcedureSchema>) {
      assertWriteAllowed();
      return omClient.post("/storedProcedures", params);
    }
  • Zod schema for the 'create-stored-procedure' tool, defining input parameters: name (required string), databaseSchema (required string), description (optional string), storedProcedureCode (optional record), tags (optional array), and owners (optional array).
    export const createStoredProcedureSchema = z.object({
      name: z.string().describe("Stored Procedure name"),
      databaseSchema: z.string().describe("FQN of the parent database schema"),
      description: z.string().optional().describe("Stored Procedure description in markdown"),
      storedProcedureCode: z.record(z.string(), z.any()).optional().describe("Stored procedure code definition (e.g. {language:'SQL', code:'...'})"),
      tags: z.array(z.record(z.string(), z.any())).optional().describe("Tags to apply"),
      owners: z.array(z.record(z.string(), z.any())).optional().describe("Owner references"),
    });
  • src/index.ts:395-395 (registration)
    Registration of the 'create-stored-procedure' tool with its name, description, schema shape, and handler wrapped via wrapToolHandler.
    tool("create-stored-procedure", "Create a new stored procedure", createStoredProcedureSchema.shape, wrapToolHandler(createStoredProcedure));
Behavior2/5

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

No annotations provided. The description does not disclose behavioral traits such as idempotency, permissions required, or side effects. For a mutation tool, this is insufficient.

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 sentence with no wasted words. However, it may be too brief to be fully informative.

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 6 parameters including nested objects (e.g., storedProcedureCode), no output schema, and no annotations. The description fails to explain return values, constraints, or how to construct nested parameters, making it insufficient for effective use.

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?

Input schema covers all 6 parameters with descriptions (100% coverage). The description adds no additional meaning beyond the schema's parameter descriptions, which are adequate but generic.

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 'Create a new stored procedure' clearly identifies the action and resource. It is specific enough, though it does not differentiate from sibling 'create-*' tools beyond the resource 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 'create-schema' or 'update-stored-procedure'. Lacks explicit context or prerequisites.

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