Skip to main content
Glama
syucream

Lightdash MCP Server

by syucream

lightdash_list_spaces

List all spaces in a Lightdash project by providing its UUID to explore project structure.

Instructions

List all spaces in a project

Input Schema

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

Implementation Reference

  • Handler case for 'lightdash_list_spaces' tool: parses projectUuid from arguments, calls GET /api/v1/projects/{projectUuid}/spaces on the Lightdash API, and returns the spaces list as JSON text.
    case 'lightdash_list_spaces': {
      const args = ListSpacesRequestSchema.parse(request.params.arguments);
      const { data, error } = await lightdashClient.GET(
        '/api/v1/projects/{projectUuid}/spaces',
        {
          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 defining the input for lightdash_list_spaces: requires a projectUuid (UUID string).
    export const ListSpacesRequestSchema = z.object({
      projectUuid: z
        .string()
        .uuid()
        .describe(
          'The UUID of the project. You can obtain it from the project list.'
        ),
    });
  • src/mcp.ts:59-63 (registration)
    Tool registration in the ListToolsRequestSchema handler, listing lightdash_list_spaces with its description and input schema.
    {
      name: 'lightdash_list_spaces',
      description: 'List all spaces in a project',
      inputSchema: zodToJsonSchema(ListSpacesRequestSchema),
    },
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 only says 'list', implying a read operation, but fails to disclose pagination, permission requirements, or whether the list is comprehensive. Minimal behavioral context.

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 sentence, concise and front-loaded. It is appropriately sized for a simple list operation, though a second sentence could clarify return format without harming brevity.

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 annotations, the description is incomplete. It does not specify response structure, pagination, or any edge cases. For a list tool in a suite of similar tools, this is insufficient for accurate selection and invocation.

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, providing its meaning and how to obtain its value. The description adds no additional insight beyond the schema, so baseline score applies.

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 clearly states the action ('List') and the resource ('spaces') with a scope ('in a project'). However, it does not differentiate from sibling tools like lightdash_list_charts or lightdash_list_dashboards, missing explicit distinction.

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. The schema parameter description indirectly tells how to get the projectUuid, but there is no mention of use cases, prerequisites, or exclusions.

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