Skip to main content
Glama
us-all

openmetadata-mcp-server

by us-all

get-pipeline-service

Retrieves pipeline service details using its fully qualified name. Accepts optional fields and deleted status filters.

Instructions

Get pipeline service by name

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fqnYesService fully qualified name
fieldsNo
includeNo

Implementation Reference

  • The handler function for 'get-pipeline-service' tool. It destructures 'fqn' (fully qualified name) from params and makes a GET request to /services/pipelineServices/name/{fqn}.
    export async function getPipelineService(params: z.infer<typeof getPipelineServiceSchema>) {
      const { fqn, ...query } = params;
      return omClient.get(`/services/pipelineServices/name/${encodeURIComponent(fqn)}`, query);
    }
  • The input schema for 'get-pipeline-service'. Defines required 'fqn' (fully qualified name) and 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(),
    });
  • src/index.ts:231-231 (registration)
    Registration of the 'get-pipeline-service' tool on the MCP server with its schema and wrapped handler.
    tool("get-pipeline-service", "Get pipeline service by name", getPipelineServiceSchema.shape, wrapToolHandler(getPipelineService));
  • Imports used by getPipelineService: zod for schema validation and omClient for HTTP requests.
    import { z } from "zod/v4";
    import { omClient } from "../client.js";
    import { assertWriteAllowed } from "./utils.js";
  • Assignment of getByNameParams as getPipelineServiceSchema, used for input validation.
    export const getPipelineServiceSchema = getByNameParams;
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states the operation without revealing whether it is read-only, any side effects, permissions required, or error conditions. The description is insufficient for the agent to understand the tool's impact.

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 extremely brief with no wasted words, but it is too short to be informative. It lacks structure and detail, which is expected for a simple tool, but given the low schema coverage, more explanation would improve usability.

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?

Despite the tool being a simple get operation, the description omits important context such as return format, the meaning of the 'include' enum, or behavior of 'fields'. Without annotations or output schema, the description should provide more completeness 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% (fqn has a description). The tool description does not add meaning for the 'fields' and 'include' parameters. It does not compensate for the missing parameter documentation, leaving the agent unclear on their usage.

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 'Get pipeline service by name' uses a specific verb (get) and resource (pipeline service) with a retrieval method (by name). It clearly distinguishes from sibling tools like 'list-pipeline-services' and 'get-pipeline', though it does not explicitly mention that it returns a single entity.

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?

The description provides no guidance on when to use this tool versus alternatives like 'list-pipeline-services' or 'search-metadata'. It does not specify prerequisites, such as needing the fully qualified name, nor does it explain the context for the other parameters.

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