Skip to main content
Glama
us-all

openmetadata-mcp-server

by us-all

get-messaging-service

Retrieve a messaging service by providing its fully qualified name. Use optional fields and include parameters to filter results.

Instructions

Get messaging service by name

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fqnYesService fully qualified name
fieldsNo
includeNo

Implementation Reference

  • The handler function that executes the 'get-messaging-service' tool logic. It destructures the 'fqn' parameter from the input, encodes it, and makes a GET request to the OpenMetadata API endpoint '/services/messagingServices/name/{fqn}'.
    export async function getMessagingService(params: z.infer<typeof getMessagingServiceSchema>) {
      const { fqn, ...query } = params;
      return omClient.get(`/services/messagingServices/name/${encodeURIComponent(fqn)}`, query);
    }
  • The input schema for 'get-messaging-service'. Uses 'getByNameParams' which requires 'fqn' (service fully qualified name) and has optional 'fields' and 'include' parameters.
    const getByNameParams = z.object({
      fqn: z.string().describe("Service fully qualified name"),
      fields: z.string().optional(),
      include: z.enum(["non-deleted", "deleted", "all"]).optional(),
    });
  • The exported schema constant 'getMessagingServiceSchema' which is assigned from 'getByNameParams'.
    export const getMessagingServiceSchema = getByNameParams;
  • src/index.ts:226-226 (registration)
    Registration of the 'get-messaging-service' tool with the MCP server. Called with the tool name, description, the schema shape, and the wrapped handler function.
    tool("get-messaging-service", "Get messaging service by name", getMessagingServiceSchema.shape, wrapToolHandler(getMessagingService));
  • src/index.ts:43-44 (registration)
    The import statement that brings in 'getMessagingServiceSchema' and 'getMessagingService' from the services module into the main index.ts file.
    listMessagingServicesSchema, listMessagingServices, getMessagingServiceSchema, getMessagingService,
    listPipelineServicesSchema, listPipelineServices, getPipelineServiceSchema, getPipelineService,
Behavior2/5

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

No annotations provided, and the description does not disclose any behavioral traits such as being read-only, authentication requirements, or side effects. For a retrieval tool, stating it is a read operation would be helpful.

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 very concise (4 words) and front-loaded with the verb and resource. However, it may be too brief; slightly more detail would not harm conciseness.

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?

No output schema exists, so the description should explain return values. It does not. Also, optional parameters like 'fields' and 'include' are left unexplained, making the tool less complete for effective use.

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 only 33% (only 'fqn' is described). The description does not clarify the 'fields' or 'include' parameters, which are left to the schema. Since coverage is low, the description should compensate but fails to do so.

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 tool gets a messaging service by name, which is a specific retrieval operation. It distinguishes from sibling tools like list-messaging-services, but could be more explicit about the resource type or scope.

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 (e.g., list-messaging-services for listing). No exclusion criteria or prerequisites mentioned.

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