Skip to main content
Glama
hald

Things MCP Server

by hald

search_advanced

Search and filter todos in the Things app by status, start date, deadline, tag, area, or type for precise task management and tracking.

Instructions

Advanced todo search with multiple filters

Args: status: Filter by todo status (incomplete, completed, canceled) start_date: Filter by start date (YYYY-MM-DD) deadline: Filter by deadline (YYYY-MM-DD) tag: Filter by tag area: Filter by area UUID type: Filter by item type (to-do, project, heading)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
areaNo
deadlineNo
start_dateNo
statusNo
tagNo
typeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'search_advanced' tool. It is registered via the @mcp.tool decorator. Constructs a search_params dictionary from optional input parameters and queries the 'things.todos' API with these filters, then formats and returns the results using format_todo.
    @mcp.tool
    async def search_advanced(
        status: str = None,
        start_date: str = None,
        deadline: str = None,
        tag: str = None,
        area: str = None,
        type: str = None
    ) -> str:
        """Advanced todo search with multiple filters
        
        Args:
            status: Filter by todo status (incomplete, completed, canceled)
            start_date: Filter by start date (YYYY-MM-DD)
            deadline: Filter by deadline (YYYY-MM-DD)
            tag: Filter by tag
            area: Filter by area UUID
            type: Filter by item type (to-do, project, heading)
        """
        search_params = {}
        if status:
            search_params["status"] = status
        if start_date:
            search_params["start_date"] = start_date
        if deadline:
            search_params["deadline"] = deadline
        if tag:
            search_params["tag"] = tag
        if area:
            search_params["area"] = area
        if type:
            search_params["type"] = type
        
        todos = things.todos(include_items=True, **search_params)
        if not todos:
            return "No matching todos found"
        
        formatted_todos = [format_todo(todo) for todo in todos]
        return "\n\n---\n\n".join(formatted_todos)
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 only states that it performs a search with filters, lacking information on permissions needed, rate limits, pagination, response format, or whether it's read-only. This is inadequate for a search tool with 6 parameters and no 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized and front-loaded, with the main purpose stated first followed by a structured list of parameters. Each sentence earns its place, though the parameter explanations could be slightly more concise (e.g., repeating 'Filter by' for each).

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?

Given the tool's complexity (6 parameters, no annotations, but with output schema), the description is partially complete. It covers parameter semantics well but lacks behavioral context and usage guidelines. The presence of an output schema means return values are documented elsewhere, reducing the burden on the description.

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?

Schema description coverage is 0%, so the description must compensate. It provides clear semantics for all 6 parameters, explaining what each filters by (e.g., 'status: Filter by todo status', 'area: Filter by area UUID'), including specific values for 'status' and 'type'. This adds significant meaning beyond the bare schema.

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 tool's purpose as 'Advanced todo search with multiple filters', specifying the verb ('search') and resource ('todo'). It distinguishes from basic search tools by emphasizing 'advanced' with multiple filters, though it doesn't explicitly differentiate from sibling tools like 'search_items' or 'search_todos'.

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 doesn't mention when this advanced search is preferable over simpler sibling tools like 'get_todos', 'search_todos', or 'search_items', nor does it specify prerequisites or exclusions for usage.

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

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

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