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

get_task

Retrieve details for a specific task by its ID to view task information within the Goodday project management platform.

Instructions

Get details of a specific task.

Args: task_id: The ID of the task to retrieve

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYes

Implementation Reference

  • The handler function decorated with @mcp.tool() that implements the 'get_task' tool. It fetches task details via the Goodday API using the provided task_id and formats the response using format_task.
    @mcp.tool()
    async def get_task(task_id: str) -> str:
        """Get details of a specific task.
    
        Args:
            task_id: The ID of the task to retrieve
        """
        data = await make_goodday_request(f"task/{task_id}")
        
        if not data:
            return "Task not found."
        
        if isinstance(data, dict) and "error" in data:
            return f"Unable to fetch task: {data.get('error', 'Unknown error')}"
        
        return format_task(data)
  • Helper function to format the raw task data into a human-readable markdown string.
    def format_task(task: dict) -> str:
        """Format a task into a readable string with safe checks."""
        if not isinstance(task, dict):
            return f"Invalid task data: {repr(task)}"
    
        # Defensive defaults in case nested keys are not dicts
        status = task.get('status') if isinstance(task.get('status'), dict) else {}
        project = task.get('project') if isinstance(task.get('project'), dict) else {}
    
        return f"""
    **Task ID:** {task.get('shortId', 'N/A')}
    **Title:** {task.get('name', 'N/A')}
    **Status:** {status.get('name', 'N/A')}
    **Project:** {project.get('name', 'N/A')}
    **Assigned To:** {task.get('assignedToUserId', 'N/A')}
    **Priority:** {task.get('priority', 'N/A')}
    **Start Date:** {task.get('startDate', 'N/A')}
    **End Date:** {task.get('endDate', 'N/A')}
    **Description:** {task.get('message', 'No description')}
    """.strip()
  • Core helper function used by get_task to make authenticated HTTP requests to the Goodday API.
    async def make_goodday_request(endpoint: str, method: str = "GET", data: dict = None, subfolders: bool = True) -> dict[str, Any] | list[Any] | None:
        """Make a request to the Goodday API with proper error handling."""
        api_token = os.getenv("GOODDAY_API_TOKEN")
        if not api_token:
            raise ValueError("GOODDAY_API_TOKEN environment variable is required")
        
        headers = {
            "User-Agent": USER_AGENT,
            "gd-api-token": api_token,
            "Content-Type": "application/json"
        }
        
        # Automatically add subfolders=true for project task and document endpoints if not already present
        if subfolders and endpoint.startswith("project/") and ("/tasks" in endpoint or "/documents" in endpoint):
            if "?" in endpoint:
                if "subfolders=" not in endpoint:
                    endpoint += "&subfolders=true"
            else:
                endpoint += "?subfolders=true"
        
        url = f"{GOODDAY_API_BASE}/{endpoint.lstrip('/')}"
        
        async with httpx.AsyncClient() as client:
            try:
                if method.upper() == "POST":
                    response = await client.post(url, headers=headers, json=data, timeout=30.0)
                elif method.upper() == "PUT":
                    response = await client.put(url, headers=headers, json=data, timeout=30.0)
                elif method.upper() == "DELETE":
                    response = await client.delete(url, headers=headers, timeout=30.0)
                else:
                    response = await client.get(url, headers=headers, timeout=30.0)
    
                response.raise_for_status()
                return response.json()
    
            except httpx.HTTPStatusError as e:
                raise Exception(f"HTTP error {e.response.status_code}: {e.response.text}")
            except httpx.RequestError as e:
                raise Exception(f"Request error: {str(e)}")
            except Exception as e:
                raise Exception(f"Unexpected error: {str(e)}")
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions retrieving task details but doesn't cover aspects like authentication needs, rate limits, error handling, or response format. This is inadequate for a tool with zero annotation coverage.

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 core purpose in the first sentence, followed by a concise parameter explanation. There is no wasted text, and the structure is clear and efficient.

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 complexity of task management tools, no annotations, no output schema, and low schema coverage, the description is insufficient. It lacks details on return values, error conditions, and how it differs from similar tools, making it incomplete for effective agent use.

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?

Schema description coverage is 0%, but the description adds minimal semantics by specifying 'task_id' as 'The ID of the task to retrieve'. This clarifies the parameter's purpose slightly beyond the schema's title 'Task Id', though it doesn't detail format or constraints. Baseline 3 is appropriate as it compensates somewhat for low coverage.

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 'details of a specific task', making the purpose evident. However, it doesn't differentiate from sibling tools like 'get_task_details' or 'get_project_tasks', which could cause confusion about scope or specificity.

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?

No guidance is provided on when to use this tool versus alternatives such as 'get_task_details' or 'get_project_tasks'. The description only states what it does, leaving the agent to infer usage context from tool names alone.

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