Skip to main content
Glama
enesjakozh
aptro

Superset MCP Integration

by aptro
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

superset_user_get_current

Retrieve the profile, permissions, and preferences of the currently authenticated user in Apache Superset.

Instructions

Get information about the currently authenticated user

Makes a request to the /api/v1/me/ endpoint to retrieve the user's profile information including permissions and preferences.

Returns: A dictionary with user profile data

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • main.py:1469-1482 (handler)
    The main handler function implementing the 'superset_user_get_current' tool. It fetches the current authenticated user's profile information from the Superset API endpoint '/api/v1/me/' using the shared make_api_request helper. Includes decorators for tool registration (@mcp.tool()), authentication requirement (@requires_auth), and error handling (@handle_api_errors). No separate input schema validation; relies on the general MCP framework.
    @mcp.tool()
@requires_auth
@handle_api_errors
async def superset_user_get_current(ctx: Context) -> Dict[str, Any]:
    """
    Get information about the currently authenticated user

    Makes a request to the /api/v1/me/ endpoint to retrieve the user's profile
    information including permissions and preferences.

    Returns:
        A dictionary with user profile data
    """
    return await make_api_request(ctx, "get", "/api/v1/me/")

Tool Definition Quality

A3.7/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses that the tool makes an API request to '/api/v1/me/' and returns a dictionary with user data, which is helpful. However, it doesn't mention behavioral traits like whether it's read-only (implied by 'Get'), potential error conditions, rate limits, or authentication requirements beyond 'authenticated user.' For a tool with zero annotation coverage, this is a moderate but incomplete disclosure.

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 well-structured and concise: it starts with the core purpose, adds implementation detail about the API endpoint, and ends with return value information. Every sentence adds value without redundancy, and it's appropriately sized for a simple tool with no parameters.

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

Completeness4/5

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

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is mostly complete. It explains what the tool does, how it works (API endpoint), and what it returns. However, it could be more complete by explicitly stating it's a read-only operation and clarifying authentication context, which would help the agent use it correctly in workflows.

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 tool has 0 parameters, and schema description coverage is 100% (though empty). The description doesn't need to add parameter semantics, so a baseline of 4 is appropriate. It correctly doesn't discuss parameters, focusing instead on the tool's purpose and behavior.

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 tool's purpose: 'Get information about the currently authenticated user' with specific details about retrieving profile information including permissions and preferences. It distinguishes itself from sibling tools like 'superset_user_get_roles' by focusing on the current user's own data rather than role management. However, it doesn't explicitly contrast with other user-related tools (none listed in siblings), so it's not a perfect 5.

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 usage context through 'currently authenticated user,' suggesting it should be used when the agent needs to identify the logged-in user's profile. However, it lacks explicit guidance on when to use this versus alternatives like checking token validity or other auth tools, and doesn't mention prerequisites (e.g., requires prior authentication). This leaves some ambiguity for the agent.

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/aptro/superset-mcp'

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