Skip to main content
Glama
us-all

openmetadata-mcp-server

by us-all

list-dashboard-services

Retrieve dashboard services from OpenMetadata with optional filtering by fields, limit, pagination, and deletion status.

Instructions

List dashboard services

Input Schema

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

Implementation Reference

  • The handler function that executes the 'list-dashboard-services' tool logic. It makes a GET request to '/services/dashboardServices' with query params (fields, limit, before, after, include).
    export async function listDashboardServices(params: z.infer<typeof listDashboardServicesSchema>) {
      return omClient.get("/services/dashboardServices", params);
    }
  • The schema (listParams) reused as listDashboardServicesSchema. Defines input validation: optional fields, limit with default 10, pagination cursors, and include filter.
    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:220-220 (registration)
    Registration of the tool with name 'list-dashboard-services', description 'List dashboard services', using the schema shape and wrapped handler.
    tool("list-dashboard-services", "List dashboard services", listDashboardServicesSchema.shape, wrapToolHandler(listDashboardServices));
Behavior2/5

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

No annotations are present, so the description bears full responsibility. It merely states the action without disclosing behavioral traits like pagination, filtering, or read-only nature. The parameters (limit, before, after) hint at paging, but the description does not acknowledge it.

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 a single short sentence, which is concise but overly minimal. It sacrifices valuable detail for brevity. A more structured explanation could 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?

Given the complexity (5 parameters, no output schema, no annotations), the description is notably incomplete. It fails to explain the concept of dashboard services, pagination, or the 'include' parameter's purpose. The agent would need to infer too much.

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?

Only 20% of the schema has description coverage (the 'fields' parameter). The tool description adds no information about parameters beyond what the schema provides. For a tool with 5 parameters, this is insufficient.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'List dashboard services' states a specific verb and resource, but lacks differentiation from sibling tools like 'list-dashboards' and 'get-dashboard-service'. It is clear enough but not distinctive.

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. Sibling tools exist that could overlap, but no context is given for selection.

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