Skip to main content
Glama
syucream

Lightdash MCP Server

by syucream

lightdash_get_user_attributes

Retrieves organization user attributes to customize analytics and apply user-specific filters.

Instructions

Get organization user attributes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler logic for 'lightdash_get_user_attributes' tool. Calls lightdashClient.GET('/api/v1/org/attributes') to fetch organization user attributes and returns the results as formatted JSON.
    case 'lightdash_get_user_attributes': {
      const { data, error } = await lightdashClient.GET(
        '/api/v1/org/attributes',
        {}
      );
      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),
          },
        ],
      };
    }
  • Schema definition for the tool. No input parameters required (empty object schema).
    export const GetUserAttributesRequestSchema = z.object({});
  • src/mcp.ts:109-113 (registration)
    Tool registration in the ListToolsRequestSchema handler. Registers the tool with name 'lightdash_get_user_attributes' and description 'Get organization user attributes'.
    {
      name: 'lightdash_get_user_attributes',
      description: 'Get organization user attributes',
      inputSchema: zodToJsonSchema(GetUserAttributesRequestSchema),
    },
Behavior2/5

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

With no annotations provided, the description alone must disclose behavioral traits. It only states 'Get', implying a read operation, but fails to mention authentication needs, data scope, or any side effects. This lack of detail is insufficient for safe invocation.

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 that clearly states the action. However, it could be slightly more informative without losing conciseness, e.g., by mentioning the return type.

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?

Given the absence of parameters and output schema, the description is minimal and adequate for a very simple tool. However, it does not specify what 'user attributes' includes or whether the result is a list or a single object, leaving some ambiguity.

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

Parameters4/5

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

The input schema has no parameters, and schema coverage is 100%. The description adds no additional meaning since there is nothing to describe. Following the baseline rule for 0 parameters, a score of 4 is appropriate.

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 'Get organization user attributes' uses a clear verb-resource structure, but it fails to differentiate from sibling tools like lightdash_get_analytics or lightdash_get_metadata. While the resource is specific, the lack of distinguishing details lowers the score from a 5.

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. The description does not mention any conditions, prerequisites, or exclusions, leaving the agent to guess the appropriate context.

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