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

get_user_action_required_tasks

Retrieve tasks requiring immediate attention for a specific user in Goodday project management, helping prioritize work and track pending actions.

Instructions

Get action required tasks for a specific user.

Args: user_id: The ID of the user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYes

Implementation Reference

  • The main handler function for the 'get_user_action_required_tasks' MCP tool. It fetches action-required tasks for the given user_id from the Goodday API endpoint 'user/{user_id}/action-required-tasks', formats each task using format_task helper, and returns a concatenated string of formatted tasks separated by '---'.
    async def get_user_action_required_tasks(user_id: str) -> str:
        """Get action required tasks for a specific user.
    
        Args:
            user_id: The ID of the user
        """
        data = await make_goodday_request(f"user/{user_id}/action-required-tasks")
        
        if not data:
            return "No action required tasks found."
        
        if isinstance(data, dict) and "error" in data:
            return f"Unable to fetch action required tasks: {data.get('error', 'Unknown error')}"
        
        if not isinstance(data, list):
            return f"Unexpected response format: {str(data)}"
        
        tasks = [format_task(task) for task in data]
        return "\n---\n".join(tasks)
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states what the tool does without mentioning permissions, rate limits, return format, or pagination. For a read operation with no annotation coverage, this is a significant gap in transparency.

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 concise and front-loaded with the main purpose in the first sentence. The additional 'Args' section is brief and relevant, though it could be integrated more seamlessly. Overall, it avoids unnecessary verbosity.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete. It does not explain what 'action required tasks' entail, how results are returned, or any behavioral traits. For a tool with one parameter but no structured support, more context is needed to be fully helpful.

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

Parameters3/5

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

The description adds minimal semantics for the 'user_id' parameter by stating it's 'The ID of the user', which is slightly more informative than the schema's 'User Id' title. With 0% schema description coverage, this provides some value, but it does not fully compensate for the lack of detailed parameter documentation.

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 the resource 'action required tasks for a specific user', making the purpose understandable. However, it does not explicitly differentiate from sibling tools like 'get_user_assigned_tasks' or 'get_task', leaving some ambiguity about what distinguishes 'action required' tasks from other task types.

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. It does not mention sibling tools like 'get_user_assigned_tasks' or 'get_task', nor does it specify prerequisites or exclusions, leaving the agent to infer usage 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/cdmx-in/goodday-mcp'

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