Skip to main content
Glama
jamesbrink

MCP Server for Coroot

get_current_user

Retrieve authenticated user details including email, roles, and accessible projects from the Coroot observability platform.

Instructions

Get current authenticated user information.

Returns information about the currently authenticated user including their email, name, roles, and accessible projects.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler function for 'get_current_user'. This is the entry point registered with FastMCP that executes the tool logic by calling the implementation wrapper.
    @mcp.tool()
    async def get_current_user() -> dict[str, Any]:
        """Get current authenticated user information.
    
        Returns information about the currently authenticated user including
        their email, name, roles, and accessible projects.
        """
        return await get_current_user_impl()  # type: ignore[no-any-return]
  • Low-level CorootClient method that implements the core logic: makes authenticated GET request to /api/user endpoint and returns the parsed user data.
    async def get_current_user(self) -> dict[str, Any]:
        """Get current authenticated user information.
    
        Returns:
            User information dictionary.
        """
        response = await self._request("GET", "/api/user")
        data: dict[str, Any] = response.json()
        return data
  • Registration of the 'get_current_user' tool using FastMCP @mcp.tool() decorator, which handles schema inference from signature and docstring.
    @mcp.tool()
    async def get_current_user() -> dict[str, Any]:
        """Get current authenticated user information.
    
        Returns information about the currently authenticated user including
        their email, name, roles, and accessible projects.
        """
        return await get_current_user_impl()  # type: ignore[no-any-return]
  • Implementation wrapper that calls the client method, adds success wrapper, and is decorated with error handler.
    async def get_current_user_impl() -> dict[str, Any]:
        """Get current authenticated user information."""
        user = await get_client().get_current_user()
        return {
            "success": True,
            "user": user,
        }
Behavior3/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It states the tool returns user information, implying a read-only operation, but does not detail authentication requirements, rate limits, or error handling. It adds basic context but lacks depth on behavioral traits.

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 front-loaded with the main purpose in the first sentence and adds details in the second. It is efficiently structured with no wasted words, making it easy to understand quickly.

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 annotations, but has an output schema), the description is mostly complete. It explains what the tool does and what information it returns, though it could benefit from more behavioral context like authentication details, but the output schema likely covers return values.

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 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately does not discuss parameters, focusing on the tool's purpose instead, which aligns with the baseline for zero parameters.

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 verb 'Get' and the resource 'current authenticated user information', specifying it returns email, name, roles, and accessible projects. It distinguishes itself from sibling tools like 'list_users' or 'get_user' (if present) by focusing on the authenticated user only, not listing or fetching other users.

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 when needing information about the authenticated user, such as for authentication checks or user-specific data. However, it does not explicitly state when to use this tool versus alternatives like 'list_users' or provide exclusions, leaving some ambiguity in 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/jamesbrink/mcp-coroot'

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