Skip to main content
Glama
us-all

openmetadata-mcp-server

by us-all

list-messaging-services

Retrieve a list of messaging services (e.g., Kafka) with customizable fields, pagination, and filters for deleted or non-deleted entries.

Instructions

List messaging services (Kafka, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsNoComma-separated fields to include
limitNo
beforeNo
afterNo
includeNonon-deleted

Implementation Reference

  • The actual handler function that executes the list-messaging-services tool logic. Makes a GET request to /services/messagingServices with the provided params.
    export async function listMessagingServices(params: z.infer<typeof listMessagingServicesSchema>) {
      return omClient.get("/services/messagingServices", params);
    }
  • The schema definition (listParams) used by listMessagingServicesSchema. Defines fields, limit, before, after, and include query parameters.
    const listParams = z.object({
      fields: z.string().optional().describe("Comma-separated fields to include"),
      limit: z.coerce.number().optional().default(10),
      before: z.string().optional(),
      after: z.string().optional(),
      include: z.enum(["non-deleted", "deleted", "all"]).optional().default("non-deleted"),
    });
  • src/index.ts:225-225 (registration)
    Where the tool 'list-messaging-services' is registered with the MCP server using the tool() function, providing its description, schema shape, and wrapped handler.
    tool("list-messaging-services", "List messaging services (Kafka, etc.)", listMessagingServicesSchema.shape, wrapToolHandler(listMessagingServices));
Behavior2/5

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

No annotations provided, and the description only indicates it lists messaging services. No mention of behavior like read-only, pagination, filtering, or auth requirements.

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?

Extremely concise at one sentence, but could add more context without becoming verbose. Slightly under-specified for the number of parameters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 5 parameters and no output schema or annotations, the description is woefully incomplete. It fails to explain pagination (before/after), filtering (include), or field selection.

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 20% (only 'fields' has a description). The tool description does not explain any parameters, leaving agents to infer from schema names and types.

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 states a specific verb 'List' and resource 'messaging services', with an example (Kafka), clearly distinguishing from siblings like list-tables or get-messaging-service. However, it lacks specificity on what constitutes a messaging service.

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 like get-messaging-service. The description does not indicate prerequisites or context for invocation.

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