Skip to main content
Glama
jamesbrink

MCP Server for Coroot

create_user

Add new user accounts with specific roles and permissions in Coroot's observability platform. Requires administrator access to configure user access.

Instructions

Create a new user (admin only).

Creates a new user account with specified role and permissions. Requires admin privileges.

Args: user_data: New user information including email, name, role

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_dataYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Primary MCP tool handler for 'create_user', registered via @mcp.tool() decorator. Delegates to internal implementation.
    async def create_user(user_data: dict[str, Any]) -> dict[str, Any]:
        """Create a new user (admin only).
    
        Creates a new user account with specified role and permissions.
        Requires admin privileges.
    
        Args:
            user_data: New user information including email, name, role
        """
        return await create_user_impl(user_data)  # type: ignore[no-any-return]
  • Internal helper function that invokes the CorootClient.create_user method and formats the response.
    async def create_user_impl(user_data: dict[str, Any]) -> dict[str, Any]:
        """Create a new user."""
        result = await get_client().create_user(user_data)
        return {
            "success": True,
            "message": "User created successfully",
            "user": result,
        }
  • CorootClient method that executes the actual HTTP POST request to /api/users endpoint to create the user.
    async def create_user(self, user_data: dict[str, Any]) -> dict[str, Any]:
        """Create a new user (admin only).
    
        Args:
            user_data: New user data with fields:
                      - email: User email
                      - name: Display name
                      - role: Admin|Editor|Viewer
                      - password: Initial password
    
        Returns:
            Created user.
        """
        # Add action field required by Coroot
        request_data = {"action": "create", **user_data}
    
        response = await self._request(
            "POST",
            "/api/users",
            json=request_data,
        )
        data: dict[str, Any] = response.json()
        return data
  • Docstring providing the tool schema description, input parameters for the MCP tool.
    """Create a new user (admin only).
    
    Creates a new user account with specified role and permissions.
    Requires admin privileges.
    
    Args:
        user_data: New user information including email, name, role
    """
  • Detailed schema documentation in client method docstring specifying exact user_data fields required.
    """Create a new user (admin only).
    
    Args:
        user_data: New user data with fields:
                  - email: User email
                  - name: Display name
                  - role: Admin|Editor|Viewer
                  - password: Initial password
    
    Returns:
        Created user.
    """
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 the admin privilege requirement and that it creates a new account, but doesn't mention potential side effects (e.g., email notifications sent), rate limits, or what happens on duplicate email addresses. It provides basic behavioral context but lacks comprehensive disclosure.

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 appropriately sized with three sentences plus an Args section. The first sentence states purpose and constraint, the second elaborates, the third reinforces the constraint, and the Args section adds parameter context. Some redundancy exists ('admin only' and 'Requires admin privileges'), but overall it's well-structured.

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 this is a mutation tool with no annotations, 0% schema coverage, but with an output schema present, the description provides adequate context. It covers the purpose, constraints, and parameter semantics. The output schema will handle return values, so the description doesn't need to explain them. It could benefit from more behavioral details but is reasonably complete.

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?

Schema description coverage is 0%, so the description must compensate. It explains that 'user_data' contains 'New user information including email, name, role', which provides meaningful semantic context beyond the generic object type in the schema. However, it doesn't detail all required fields or format constraints.

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 specific action ('Create a new user account') and resource ('user'), distinguishing it from sibling tools like 'list_users' or 'update_current_user'. It provides a complete verb+resource+scope combination that is unambiguous.

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

Usage Guidelines4/5

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

The description explicitly states 'admin only' and 'Requires admin privileges', providing clear context about when to use this tool (admin operations). However, it doesn't specify when NOT to use it or mention alternatives like 'update_current_user' for modifying existing users.

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