Skip to main content
Glama
cdmx-in
by cdmx-in

get_users

Retrieve organization user lists from the Goodday project management platform to access team member information for context-aware applications.

Instructions

Get list of organization users.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'get_users' MCP tool. It fetches the list of users from the Goodday API endpoint '/users', handles errors and unexpected formats, formats each user using the format_user helper, and joins them with separators for readable output.
    async def get_users() -> str:
        """Get list of organization users."""
        data = await make_goodday_request("users")
        
        if not data:
            return "No users found."
        
        if isinstance(data, dict) and "error" in data:
            return f"Unable to fetch users: {data.get('error', 'Unknown error')}"
        
        if not isinstance(data, list):
            return f"Unexpected response format: {str(data)}"
        
        users = [format_user(user) for user in data]
        return "\n---\n".join(users)
  • Helper function used by get_users to format individual user data into a multi-line string displaying key fields like ID, name, email, role, and status with defensive checks.
    def format_user(user: dict) -> str:
        """Format a user into a readable string with safe checks."""
        if not isinstance(user, dict):
            return f"Invalid user data: {repr(user)}"
    
        # Defensive defaults in case nested keys are not dicts
        role = user.get('role') if isinstance(user.get('role'), dict) else {}
    
        return f"""
    User ID: {user.get('id', 'N/A')}
    Name: {user.get('name', 'N/A')}
    Email: {user.get('email', 'N/A')}
    Role: {role.get('name', 'N/A')}
    Status: {user.get('status', 'N/A')}
    """.strip()
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It states it 'gets' data (implied read-only) but doesn't cover pagination, sorting, filtering, rate limits, authentication needs, or what 'organization users' entails (e.g., active vs. all).

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 a single, efficient sentence with no wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly.

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?

For a simple read tool with no parameters and no output schema, the description is minimally adequate but lacks depth. It doesn't explain return format (e.g., list structure, fields) or behavioral context, leaving gaps for an agent to infer usage.

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 with 100% schema coverage, so no parameter documentation is needed. The description doesn't add parameter details, but that's appropriate here, earning a baseline high score for simplicity.

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 verb ('Get') and resource ('list of organization users'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get_user' (singular) or 'get_project_users', which could cause confusion about scope.

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?

The description provides no guidance on when to use this tool versus alternatives like 'get_user' (for a single user) or 'get_project_users' (for users in a specific project). There's no mention of prerequisites, context, 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/cdmx-in/goodday-mcp'

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