Skip to main content
Glama
us-all

openmetadata-mcp-server

by us-all

list-metrics

Retrieve paginated lists of business and operational metrics, with options to filter by fields, include deleted entities, and navigate using cursors.

Instructions

List business/operational Metrics (OM 1.12+) with pagination

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsNoComma-separated fields to include
limitNoNumber of results per page
beforeNoCursor for backward pagination
afterNoCursor for forward pagination
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

  • Handler function that calls the OpenMetadata API /metrics endpoint to list metrics with pagination, applying default field extraction unless extractFields is provided.
    export async function listMetrics(params: z.infer<typeof listMetricsSchema>) {
      const { extractFields, ...query } = params;
      const data = await omClient.get("/metrics", query);
      if (extractFields) return data;
      return applyExtractFields(data, DEFAULTS.metric.list);
    }
  • Zod schema defining the input parameters for list-metrics: fields, limit, before, after cursors, include deleted, and extractFields.
    export const listMetricsSchema = z.object({
      fields: z.string().optional().describe("Comma-separated fields to include"),
      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"),
      include: listIncludeEnum.optional().default("non-deleted").describe("Include deleted entities"),
      extractFields: z.string().optional().describe(extractFieldsDescription),
    });
  • src/index.ts:440-440 (registration)
    Registration of the list-metrics tool with MCP server, binding the schema and handler.
    tool("list-metrics", "List business/operational Metrics (OM 1.12+) with pagination", listMetricsSchema.shape, wrapToolHandler(listMetrics));
  • Default field projection for metrics list (used by applyExtractFields helper when caller doesn't provide extractFields).
    metric: {
      list: `${COMMON_LIST_FIELDS},data.*.metricExpression,data.*.metricType,data.*.granularity,data.*.unitOfMeasurement`,
      get:  `${COMMON_GET_FIELDS},metricExpression,metricType,granularity,unitOfMeasurement,relatedMetrics`,
    },
Behavior2/5

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

No annotations are provided, so the description bears full responsibility. It mentions 'List' and 'pagination' but does not disclose that this is a read-only operation, authentication needs, rate limits, or any side effects. Behavioral traits are largely absent.

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?

The description is a single 16-word sentence that efficiently conveys purpose and pagination. No redundant words; every part earns its place.

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?

The description omits important context such as what constitutes a metric, the significance of OM 1.12+, the structure of paginated responses, and behavior of the 'include' parameter. For a tool with 6 parameters, more context is needed.

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 100% and parameter descriptions are already detailed (e.g., extractFields explains dotted paths). The description adds no additional parameter meaning beyond the schema, so baseline 3 is appropriate.

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), the resource (business/operational Metrics), includes a version hint (OM 1.12+), and mentions pagination. This clearly differentiates from sibling list tools and the get-metric-by-name tool.

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 vs alternatives. There is no mention of prerequisites, exclusions, or when not to use it. Siblings like search-metadata or suggest-metadata could be alternatives but are not addressed.

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