Skip to main content
Glama

get_task_notes

Retrieve all notes for a task by providing its name, task ID, series ID, or list ID.

Instructions

Get all notes for a task.

Args: task_name: Task name to search for task_id: Specific task ID taskseries_id: Task series ID list_id: List ID

Returns: List of notes for the task

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_nameNo
task_idNo
taskseries_idNo
list_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The actual handler function for the get_task_notes tool. It takes task_name, task_id, taskseries_id, or list_id to find a task, retrieves its notes from the RTM API, and formats them by id, title, body, created, and modified.
    async def get_task_notes(
        ctx: Context,
        task_name: str | None = None,
        task_id: str | None = None,
        taskseries_id: str | None = None,
        list_id: str | None = None,
    ) -> dict[str, Any]:
        """Get all notes for a task.
    
        Args:
            task_name: Task name to search for
            task_id: Specific task ID
            taskseries_id: Task series ID
            list_id: List ID
    
        Returns:
            List of notes for the task
        """
        from ..client import RTMClient
    
        client: RTMClient = await get_client()
    
        # Find the task with its notes
        if task_name and not task_id:
            result = await client.call("rtm.tasks.getList")
            tasks = parse_tasks_response(result)
    
            name_lower = task_name.lower()
            task = None
            for t in tasks:
                if t["name"].lower() == name_lower or name_lower in t["name"].lower():
                    task = t
                    break
    
            if not task:
                return build_response(data={"error": f"Task not found: {task_name}"})
        else:
            if not all([task_id, taskseries_id, list_id]):
                return build_response(
                    data={"error": "Must provide task_name or all three IDs"},
                )
            # Fetch the specific task
            result = await client.call("rtm.tasks.getList", list_id=list_id)
            tasks = parse_tasks_response(result)
            task = None
            for t in tasks:
                if t["id"] == task_id and t["taskseries_id"] == taskseries_id:
                    task = t
                    break
    
            if not task:
                return build_response(data={"error": "Task not found"})
    
        notes = task.get("notes", [])
        if isinstance(notes, dict):
            notes = [notes]
    
        formatted_notes = []
        for note in notes:
            formatted_notes.append(
                {
                    "id": note.get("id"),
                    "title": note.get("title", ""),
                    "body": note.get("$t", note.get("body", "")),
                    "created": note.get("created"),
                    "modified": note.get("modified"),
                }
            )
    
        return build_response(
            data={
                "task_name": task.get("name"),
                "notes": formatted_notes,
                "count": len(formatted_notes),
            },
        )
  • Input schema for get_task_notes: accepts optional task_name, task_id, taskseries_id, list_id parameters. Returns a dict with task_name, notes list, and count.
    async def get_task_notes(
        ctx: Context,
        task_name: str | None = None,
        task_id: str | None = None,
        taskseries_id: str | None = None,
        list_id: str | None = None,
    ) -> dict[str, Any]:
  • The register_note_tools function is the registration mechanism. It calls @mcp.tool() decorator on the get_task_notes function to register it with the FastMCP server.
    def register_note_tools(mcp: Any, get_client: Any) -> None:
        """Register all note-related tools."""
  • Registration invocation: register_note_tools(mcp, get_client) in server.py triggers registration of the get_task_notes tool.
    register_note_tools(mcp, get_client)
    register_utility_tools(mcp, get_client)
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions it is a read operation but does not disclose any behavioral traits such as side effects, prerequisites, rate limits, or whether the operation is idempotent.

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 with a docstring structure including Args and Returns. It is front-loaded with the purpose. However, it could be slightly more efficient by removing the redundant 'Args' line.

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?

Despite the presence of an output schema, the description lacks critical usage context. It does not explain how the four optional parameters work together, whether one is sufficient, or typical use cases. For a retrieval tool with multiple optional identifiers, this is incomplete.

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?

With 0% schema coverage, the description adds basic meaning by labeling each parameter (e.g., 'Task name to search for'). However, it does not clarify how parameters relate or whether any combination is required, leaving ambiguity.

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 'Get all notes for a task', which is a specific verb and resource. It distinguishes itself from sibling tools like add_note, delete_note, and edit_note by focusing on retrieval.

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 for retrieving notes but does not provide explicit guidance on when to use each parameter or alternatives. There is no mention of orchestration with other note tools.

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/ljadach/rtm-mcp'

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