Skip to main content
Glama
elizagarate

Things MCP Server

by elizagarate

search_todos

Find todos by matching a query against titles and notes.

Instructions

Search todos by title or notes

Args: query: Search term to look for in todo titles and notes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The actual handler function for the 'search_todos' tool. It is decorated with @mcp.tool, takes a query string parameter, calls things.search(query, include_items=True), formats the results using format_todo, and returns them as a string.
    async def search_todos(query: str) -> str:
        """Search todos by title or notes
    
        Args:
            query: Search term to look for in todo titles and notes
        """
        todos = things.search(query, include_items=True)
        if not todos:
            return f"No todos found matching '{query}'"
    
        formatted_todos = [format_todo(todo) for todo in todos]
        return "\n\n---\n\n".join(formatted_todos)
  • The @mcp.tool decorator registers 'search_todos' as an MCP tool on the FastMCP server instance.
    @mcp.tool
  • The format_todo helper is imported from formatters and used inside search_todos to format each todo result.
    from .formatters import format_todo, format_project, format_area, format_tag, format_heading
  • The docstring serves as the schema/description for the tool, defining query as the only parameter for searching todos by title or notes.
    """Search todos by title or notes
    
    Args:
        query: Search term to look for in todo titles and notes
Behavior2/5

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

No annotations provided, so the description must fully cover behavior. It only states the search scope but omits details on case sensitivity, pagination, result ordering, authentication needs, or performance implications.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is very short and front-loaded with the key action. However, it is under-specified and could include more detail without losing conciseness.

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 the tool set and presence of many sibling tools, the description is incomplete. It does not explain the search scope (title/notes only), match behavior, or result format, even though an output schema exists.

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

Parameters2/5

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

The input schema has 0% description coverage for the query parameter. The description adds a brief explanation ('Search term to look for in todo titles and notes'), which provides some meaning beyond the schema but is minimal.

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 it searches todos by title or notes, providing a specific verb and resource. It implicitly distinguishes from siblings like search_advanced and search_items, but does not explicitly differentiate, which would warrant a 5.

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 on when to use this tool versus alternatives (e.g., search_advanced, get_todos). The description lacks any context for appropriate use or exclusions.

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