Skip to main content
Glama
us-all

openmetadata-mcp-server

by us-all

get-event-subscription-by-name

Get event subscription details by name, optionally specifying fields and inclusion status.

Instructions

Get event subscription by name

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesEvent Subscription name
fieldsNoComma-separated fields to include
includeNo

Implementation Reference

  • The handler function for get-event-subscription-by-name. Extracts the 'name' from params, constructs an API GET request to `/events/subscriptions/name/{encodedName}` using omClient.
    export async function getEventSubscriptionByName(params: z.infer<typeof getEventSubscriptionByNameSchema>) {
      const { name, ...query } = params;
      return omClient.get(`/events/subscriptions/name/${encodeURIComponent(name)}`, query);
    }
  • The Zod schema for get-event-subscription-by-name, defining input parameters: name (required string), fields (optional string), and include (optional enum).
    export const getEventSubscriptionByNameSchema = z.object({
      name: z.string().describe("Event Subscription name"),
      fields: z.string().optional().describe("Comma-separated fields to include"),
      include: z.enum(["non-deleted", "deleted", "all"]).optional(),
    });
  • src/index.ts:412-412 (registration)
    Registration of the tool in the MCP server using the tool() function with schema and wrapped handler.
    tool("get-event-subscription-by-name", "Get event subscription by name", getEventSubscriptionByNameSchema.shape, wrapToolHandler(getEventSubscriptionByName));
  • src/index.ts:124-124 (registration)
    Import statement that brings in getEventSubscriptionByNameSchema and getEventSubscriptionByName from the events module.
    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?

With no annotations, the description should disclose behavioral traits like return format, error handling, or authentication requirements. It only states that it 'gets' an event subscription by name, but provides no details on side effects, read-only nature, or response structure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very concise (one sentence) but lacks substance. It repeats the tool name's implied functionality without adding value. It is not wasteful but could be expanded to be more informative.

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 no output schema, no annotations, and 3 parameters, the description is incomplete. It does not explain what the returned event subscription contains, how pagination works, or any edge cases. The agent would have to infer from context or trial and error.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 67% (name and fields have descriptions, include only has enum values). The description adds no additional meaning beyond the schema; it does not explain the fields or include parameter semantics or how they affect the result.

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 ('Get') and the resource ('event subscription') with the specific retrieval key ('by name'). It distinguishes from sibling tools like get-event-subscription (which likely retrieves by other means) and other get-*-by-name tools for different entities.

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 such as get-event-subscription or list-events. The description does not help the agent select the correct tool based on context.

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