Skip to main content
Glama
syucream

Lightdash MCP Server

by syucream

lightdash_get_catalog

Retrieve the catalog of analytics assets for a project, including charts, dashboards, and metrics, using the project UUID.

Instructions

Get catalog for a project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectUuidYesThe UUID of the project. You can obtain it from the project list.

Implementation Reference

  • src/mcp.ts:79-83 (registration)
    Tool registration in the ListTools handler — defines name, description, and input schema for lightdash_get_catalog.
    {
      name: 'lightdash_get_catalog',
      description: 'Get catalog for a project',
      inputSchema: zodToJsonSchema(GetCatalogRequestSchema),
    },
  • Handler for the 'lightdash_get_catalog' tool call — parses arguments via GetCatalogRequestSchema and calls Lightdash API GET /api/v1/projects/{projectUuid}/dataCatalog, returning results as JSON.
    case 'lightdash_get_catalog': {
      const args = GetCatalogRequestSchema.parse(request.params.arguments);
      const { data, error } = await lightdashClient.GET(
        '/api/v1/projects/{projectUuid}/dataCatalog',
        {
          params: {
            path: {
              projectUuid: args.projectUuid,
            },
          },
        }
      );
      if (error) {
        throw new Error(
          `Lightdash API error: ${error.error.name}, ${
            error.error.message ?? 'no message'
          }`
        );
      }
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(data.results, null, 2),
          },
        ],
      };
    }
  • Input schema (Zod) for the lightdash_get_catalog tool — requires a projectUuid (UUID string).
    export const GetCatalogRequestSchema = z.object({
      projectUuid: z
        .string()
        .uuid()
        .describe(
          'The UUID of the project. You can obtain it from the project list.'
        ),
    });
  • Import of GetCatalogRequestSchema from schemas.js used by both registration and handler.
      GetCatalogRequestSchema,
      GetMetricsCatalogRequestSchema,
      GetChartsAsCodeRequestSchema,
      GetDashboardsAsCodeRequestSchema,
      GetMetadataRequestSchema,
      GetAnalyticsRequestSchema,
      GetUserAttributesRequestSchema,
    } from './schemas.js';
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 only states the operation is a 'get' but does not mention read-write behavior, required permissions, error conditions, or side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is too terse—a single, vague sentence. While brevity is valued, it lacks essential structure or elaboration that would help an agent use it correctly.

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 output schema and the presence of similar sibling tools, the description is incomplete. It does not explain what the catalog consists of or how it differs from closely related 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 100% for the single parameter, and the schema already provides a clear description. The tool description adds no additional meaning beyond what the schema states.

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 'Get catalog for a project' uses a specific verb and resource, but 'catalog' is ambiguous without context; it does not explain what the catalog contains. It partially distinguishes from siblings like get_metrics_catalog but doesn't clarify the difference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No usage guidelines are provided. There is no indication of when to use this tool versus siblings like lightdash_get_metrics_catalog or lightdash_get_project.

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/syucream/lightdash-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server