Skip to main content
Glama
elizagarate

Things MCP Server

by elizagarate

get_todos

Retrieve todos from your Things 3 task manager. Filter by project UUID and optionally include checklist items.

Instructions

Get todos from Things, optionally filtered by project

Args: project_uuid: Optional UUID of a specific project to get todos from include_items: Include checklist items

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_uuidNo
include_itemsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The get_todos async function that executes the tool logic. It fetches todos from Things via `things.todos()`, optionally filtered by project_uuid, and returns formatted strings.
    async def get_todos(project_uuid: str = None, include_items: bool = True) -> str:
        """Get todos from Things, optionally filtered by project
    
        Args:
            project_uuid: Optional UUID of a specific project to get todos from
            include_items: Include checklist items
        """
        if project_uuid:
            project = things.get(project_uuid)
            if not project or project.get('type') != 'project':
                return f"Error: Invalid project UUID '{project_uuid}'"
    
        todos = things.todos(project=project_uuid, start=None, include_items=include_items)
        if not todos:
            return "No todos found"
    
        formatted_todos = [format_todo(todo) for todo in todos]
        return "\n\n---\n\n".join(formatted_todos)
  • The @mcp.tool decorator registers get_todos as an MCP tool with FastMCP.
    @mcp.tool
    async def get_todos(project_uuid: str = None, include_items: bool = True) -> str:
  • Test that verifies get_todos includes checklist items and calls things.todos() with correct parameters.
    result = await get_todos.fn(include_items=True)
    
    assert "Checklist:" in result
    assert "First item" in result
    mock_things_todos.assert_called_once_with(project=None, start=None, include_items=True)
Behavior2/5

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

No annotations provided, so description must fully disclose behavior. It states only 'Get todos' without mentioning side effects, authentication needs, rate limits, or output structure. Minimal disclosure for a read operation.

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?

Description is concise with a clear purpose sentence and an args section. It front-loads the main action and efficiently lists parameters, though minor tightening could remove redundancy in the parameter descriptions.

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 tool with two optional parameters and an output schema, the description covers basic functionality but lacks usage context among many sibling tools. Behavioral details like read-only nature are absent, making it adequate but not fully complete.

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 coverage is 0%, but the description adds meaning by explaining project_uuid as an optional UUID for filtering and include_items as including checklist items. This partially compensates for the schema's lack of description, providing some context beyond types and defaults.

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?

Description clearly states it gets todos from Things with optional project filter. The verb 'Get' and resource 'todos' are specific, and the optional filter distinguishes it from sibling tools like get_today or get_inbox.

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 explicit guidance on when to use this tool versus alternatives such as get_today, get_inbox, or get_projects. The description mentions an optional project filter but does not clarify scenarios where other tools are preferable.

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/elizagarate/things-mcp'

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