Skip to main content
Glama
us-all

openmetadata-mcp-server

by us-all

list-events

Retrieve event subscriptions with pagination support, field selection, and option to include deleted or all entities.

Instructions

List event subscriptions

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

Implementation Reference

  • The listEvents async function that executes the tool logic by making a GET request to /events/subscriptions with the provided parameters.
    export async function listEvents(params: z.infer<typeof listEventsSchema>) {
      return omClient.get("/events/subscriptions", params);
    }
  • Zod schema defining input parameters for list-events: fields, limit (default 10), before/after cursors for pagination, and include filter (non-deleted by default).
    export const listEventsSchema = 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: z.enum(["non-deleted", "deleted", "all"]).optional().default("non-deleted").describe("Include deleted entities"),
    });
  • src/index.ts:410-410 (registration)
    Registration of the 'list-events' tool via the tool() function, wiring the schema and handler together with a description 'List event subscriptions'.
    tool("list-events", "List event subscriptions", listEventsSchema.shape, wrapToolHandler(listEvents));
  • src/index.ts:124-124 (registration)
    Import of listEventsSchema and listEvents from ./tools/events.js into the registration file.
    import { listEventsSchema, listEvents, getEventSubscriptionSchema, getEventSubscription, getEventSubscriptionByNameSchema, getEventSubscriptionByName } from "./tools/events.js";
Behavior2/5

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

No annotations are present, so the description should disclose behavioral traits. It only states 'List' implying read-only, but does not elaborate on pagination behavior, sorting, filtering beyond stdin, or any side effects. This is minimal disclosure.

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 concise sentence with no filler. Every word serves a purpose.

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 presence of five parameters (pagination, fields, delete filter) and no output schema, the description fails to explain how to use these parameters effectively or what the response contains. It lacks context about the nature of 'event subscriptions' and how this list operation integrates with other tools.

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?

All five parameters have descriptions in the input schema (100% coverage). The description adds no additional meaning beyond what the schema already provides, so baseline score of 3 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?

Description 'List event subscriptions' clearly identifies the action (list) and resource (event subscriptions). It distinguishes from sibling tools like 'get-event-subscription' which are singular fetch operations. However, the term 'event subscriptions' is not further explained, leaving some ambiguity.

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 such as 'get-event-subscription' or 'get-event-subscription-by-name'. The description does not mention use cases or when not to use it.

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