Skip to main content
Glama
us-all

openmetadata-mcp-server

by us-all

list-ml-models

Retrieve a paginated list of machine learning models, filtered by service. Supports cursor navigation and custom field projections.

Instructions

List ML models with pagination and service filtering

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsNoComma-separated fields to include (e.g. 'owners,tags,followers')
limitNoNumber of results per page
beforeNoCursor for backward pagination
afterNoCursor for forward pagination
serviceNoFilter by service FQN
includeNoInclude deleted entitiesnon-deleted
extractFieldsNoComma-separated dotted paths to project from response (e.g. 'id,name,owner.name,columns.*.name'). Use `*` as wildcard for arrays/objects. Wrap field names with dots in backticks. Reduces response tokens dramatically on large entities.

Implementation Reference

  • The handler function for list-ml-models. Makes a GET request to /mlmodels with pagination and filtering parameters.
    export async function listMlModels(params: z.infer<typeof listMlModelsSchema>) {
      return omClient.get("/mlmodels", params);
    }
  • The Zod schema (listMlModelsSchema) defining input parameters: fields, limit, before, after, service, include, and extractFields.
    export const listMlModelsSchema = z.object({
      fields: z.string().optional().describe("Comma-separated fields to include (e.g. 'owners,tags,followers')"),
      limit: z.coerce.number().optional().default(10).describe("Number of results per page"),
      before: z.string().optional().describe("Cursor for backward pagination"),
      after: z.string().optional().describe("Cursor for forward pagination"),
      service: z.string().optional().describe("Filter by service FQN"),
      include: z.enum(["non-deleted", "deleted", "all"]).optional().default("non-deleted").describe("Include deleted entities"),
      extractFields: ef,
    });
  • src/index.ts:310-310 (registration)
    Registration of the 'list-ml-models' tool via the tool() helper, with description and schema shape, categorized under 'mlmodels'.
    tool("list-ml-models", "List ML models with pagination and service filtering", listMlModelsSchema.shape, wrapToolHandler(listMlModels));
  • src/index.ts:82-85 (registration)
    Import of listMlModelsSchema and listMlModels from ./tools/mlmodels.js.
      listMlModelsSchema, listMlModels, getMlModelSchema, getMlModel,
      getMlModelByNameSchema, getMlModelByName, createMlModelSchema, createMlModel,
      updateMlModelSchema, updateMlModel, deleteMlModelSchema, deleteMlModel,
    } from "./tools/mlmodels.js";
  • Mention of list-ml-models in a prompt template guiding users to enumerate assets under a domain.
    "   - `list-ml-models`",
Behavior2/5

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

No annotations are provided, so the description must fully convey behavioral traits. It mentions pagination and filtering but does not disclose whether the operation is read-only, required permissions, rate limits, or response structure, leaving significant gaps.

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 with the core action. It is efficient but could be slightly more informative without becoming verbose.

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 7 parameters, no output schema, and no annotations, the description is incomplete. It does not cover sorting, default behavior, error conditions, or relationship to other entities, leaving the agent underinformed.

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 description coverage is 100%, so the baseline is 3. The description adds no additional meaning beyond what the parameter descriptions already provide; it merely summarizes 'pagination and service filtering' without enriching 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 'List ML models with pagination and service filtering' clearly states the action (list) and the resource (ML models), and distinguishes from sibling list tools by specifying pagination and filtering capabilities.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for listing ML models with optional pagination and filtering, but does not explicitly state when to use this tool versus alternatives like get-ml-model or other list tools, nor does it provide 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