Skip to main content
Glama
us-all

openmetadata-mcp-server

by us-all

get-dashboard-by-name

Retrieve a specific dashboard by its fully qualified name, with options to include custom fields, filter by deletion status, and project selected data.

Instructions

Get dashboard by fully qualified name

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fqnYesFully qualified name (e.g. 'service.dashboardName')
fieldsNoComma-separated fields to include
includeNo
extractFieldsNoComma-separated dotted paths to project from response (e.g. 'id,name,owner.name,columns.*.name'). Use `*` as wildcard for arrays/objects. Wrap field names with dots in backticks. Reduces response tokens dramatically on large entities.

Implementation Reference

  • Zod schema for get-dashboard-by-name tool input validation. Defines parameters: fqn (required string, fully qualified name), fields (optional string), include (optional enum), and extractFields (optional string).
    export const getDashboardByNameSchema = z.object({
      fqn: z.string().describe("Fully qualified name (e.g. 'service.dashboardName')"),
      fields: z.string().optional().describe("Comma-separated fields to include"),
      include: z.enum(["non-deleted", "deleted", "all"]).optional(),
      extractFields: z.string().optional().describe(extractFieldsDescription),
    });
  • Handler function that executes the get-dashboard-by-name tool. Accepts parameters validated by getDashboardByNameSchema, constructs a GET request to `/dashboards/name/{fqn}`, and returns the dashboard data with optional field extraction using applyExtractFields.
    export async function getDashboardByName(params: z.infer<typeof getDashboardByNameSchema>) {
      const { fqn, extractFields, ...query } = params;
      const data = await omClient.get(`/dashboards/name/${encodeURIComponent(fqn)}`, query);
      return applyExtractFields(data, extractFields ?? GET_DASHBOARD_DEFAULT_FIELDS);
    }
  • src/index.ts:262-270 (registration)
    Tool registration in the MCP server. The tool 'get-dashboard-by-name' is registered under the 'discovery' category with description 'Get dashboard by fully qualified name', using getDashboardByNameSchema for input validation and getDashboardByName wrapped in wrapToolHandler as the handler.
    // --- Dashboards ---
    currentCategory = "discovery";
    
    tool("list-dashboards", "List dashboards with pagination and service filtering", listDashboardsSchema.shape, wrapToolHandler(listDashboards));
    tool("get-dashboard", "Get dashboard details by UUID", getDashboardSchema.shape, wrapToolHandler(getDashboard));
    tool("get-dashboard-by-name", "Get dashboard by fully qualified name", getDashboardByNameSchema.shape, wrapToolHandler(getDashboardByName));
    tool("create-dashboard", "Create a new dashboard", createDashboardSchema.shape, wrapToolHandler(createDashboard));
    tool("update-dashboard", "Update a dashboard using JSON Patch operations", updateDashboardSchema.shape, wrapToolHandler(updateDashboard));
    tool("delete-dashboard", "Delete a dashboard by UUID", deleteDashboardSchema.shape, wrapToolHandler(deleteDashboard));
  • Imports and constant GET_DASHBOARD_DEFAULT_FIELDS used by the handler. The handler uses applyExtractFields (imported from extract-fields.ts) with this default field set when extractFields is not provided.
    import { z } from "zod/v4";
    import { omClient } from "../client.js";
    import { assertWriteAllowed } from "./utils.js";
    import { applyExtractFields, extractFieldsDescription } from "./extract-fields.js";
    
    const GET_DASHBOARD_DEFAULT_FIELDS = "id,name,fullyQualifiedName,description,owners,charts,tags";
Behavior2/5

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

With no annotations provided and no output schema, the description lacks behavioral details such as error handling, data freshness, or response structure. It only states the basic retrieval action without disclosing any operational traits.

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 a single, concise sentence with no redundant words. However, it could be slightly expanded to include key usage context without becoming verbose.

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 lack of annotations, output schema, and the tool's 4 parameters, the description is insufficiently complete. It omits return value characteristics, error conditions, and differentiation from similar get-dashboard tools.

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

Parameters3/5

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

Schema description coverage is high (75%). The description does not add meaning beyond what the schema already provides; e.g., 'fqn' is already described in the schema. Thus, it meets the baseline but does not exceed it.

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

Purpose5/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 (dashboard) with the distinguishing qualifier 'by fully qualified name'. This differentiates it from sibling tools like get-dashboard (likely by ID) 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-dashboard. The description does not mention any prerequisites, scope limitations, or explicit conditions 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