Skip to main content
Glama
us-all

openmetadata-mcp-server

by us-all

create-ml-model

Create a new ML model in OpenMetadata by providing its name, service, and algorithm. Optionally add features, target, description, tags, and owners.

Instructions

Create a new ML model

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesML Model name
serviceYesFQN of the ML model service
algorithmYesAlgorithm used by the ML model
descriptionNoML Model description in markdown
displayNameNoDisplay name
mlFeaturesNoML features definitions
targetNoTarget column or value
tagsNoTags to apply
ownersNoOwner references

Implementation Reference

  • Handler function for create-ml-model tool. Calls assertWriteAllowed() to verify write access, then POSTs the params to /mlmodels endpoint to create a new ML model.
    export async function createMlModel(params: z.infer<typeof createMlModelSchema>) {
      assertWriteAllowed();
      return omClient.post("/mlmodels", params);
    }
  • Zod schema for create-ml-model defining required fields (name, service, algorithm) and optional fields (description, displayName, mlFeatures, target, tags, owners).
    export const createMlModelSchema = z.object({
      name: z.string().describe("ML Model name"),
      service: z.string().describe("FQN of the ML model service"),
      algorithm: z.string().describe("Algorithm used by the ML model"),
      description: z.string().optional().describe("ML Model description in markdown"),
      displayName: z.string().optional().describe("Display name"),
      mlFeatures: z.array(z.record(z.string(), z.any())).optional().describe("ML features definitions"),
      target: z.string().optional().describe("Target column or value"),
      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:313-313 (registration)
    Registration of the create-ml-model tool on the MCP server, wired with the schema and handler. Category is 'ML Models' (currentCategory unset, inheriting from previous ML Models section).
    tool("create-ml-model", "Create a new ML model", createMlModelSchema.shape, wrapToolHandler(createMlModel));
Behavior2/5

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

With no annotations provided, the description alone must disclose behavioral traits. It only states the obvious action of creation, omitting any side effects (e.g., mutation of state), required permissions, or rate limits. The agent learns nothing beyond the tool's basic effect.

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, front-loaded and free of superfluous content. It is appropriately concise for a simple operation, though it could be more informative without sacrificing brevity.

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 tool has 9 parameters and no output schema, the description is insufficiently complete. It does not explain return values (e.g., created model ID), prerequisites, or any constraints, leaving the agent with gaps in understanding how to use the tool effectively.

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?

The input schema has 100% description coverage for its 9 parameters, so the schema already documents parameter meanings. The description adds no additional value beyond the schema, meeting the baseline for high coverage.

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 ('Create') and resource ('new ML model'), which is distinct from sibling tools like 'update-ml-model' and 'delete-ml-model'. However, it does not differentiate from other 'create-*' tools in the sibling list, lacking specificity about the ML domain.

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 (e.g., update-ml-model, other creation tools). The description gives no context about prerequisites, such as needing a model service or schema to exist first.

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