Skip to main content
Glama
syucream

Lightdash MCP Server

by syucream

lightdash_list_charts

Lists all charts in a Lightdash project by providing its UUID.

Instructions

List all charts in a project

Input Schema

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

Implementation Reference

  • Handler for 'lightdash_list_charts' tool. Parses args with ListChartsRequestSchema, calls Lightdash GET /api/v1/projects/{projectUuid}/charts, and returns the charts data.
    case 'lightdash_list_charts': {
      const args = ListChartsRequestSchema.parse(request.params.arguments);
      const { data, error } = await lightdashClient.GET(
        '/api/v1/projects/{projectUuid}/charts',
        {
          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),
          },
        ],
      };
    }
  • Zod schema for the ListChartsRequest. Defines a single required field: projectUuid (UUID string).
    export const ListChartsRequestSchema = z.object({
      projectUuid: z
        .string()
        .uuid()
        .describe(
          'The UUID of the project. You can obtain it from the project list.'
        ),
    });
  • src/mcp.ts:64-68 (registration)
    Tool registration in the tools list. Defines name, description, and inputSchema for 'lightdash_list_charts'.
    {
      name: 'lightdash_list_charts',
      description: 'List all charts in a project',
      inputSchema: zodToJsonSchema(ListChartsRequestSchema),
    },
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'list all charts' indicating a read operation, but lacks details on pagination, ordering, error handling, or what happens if the project is invalid. The behavioral coverage is minimal.

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

Conciseness5/5

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

The description is a single, concise sentence with no unnecessary words. It efficiently conveys the tool's purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple list tool with one parameter and no output schema, the description is somewhat complete but lacks details on return format or any constraints. Given low complexity, it is adequate but not thorough.

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?

The input schema covers 100% of parameters with a clear description for projectUuid. The description adds no additional meaning beyond the schema, so it meets the baseline for high schema coverage.

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 (list), the resource (charts), and the scope (in a project). It distinguishes from sibling tools like lightdash_list_dashboards and lightdash_list_projects.

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

Usage Guidelines3/5

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

The description implies the tool requires a projectUuid but does not specify when to use this tool versus alternatives like lightdash_get_charts_as_code or lightdash_list_dashboards. No explicit when-not or alternative guidance.

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