Skip to main content
Glama
elizagarate

Things MCP Server

by elizagarate

get_projects

Retrieve all projects from Things 3. Optionally include tasks within each project.

Instructions

Get all projects from Things

Args: include_items: Include tasks within projects

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
include_itemsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Handler function that retrieves all projects from Things via `things.projects()` and formats them using `format_project`. Registered as an MCP tool via the @mcp.tool decorator.
    @mcp.tool
    async def get_projects(include_items: bool = False) -> str:
        """Get all projects from Things
    
        Args:
            include_items: Include tasks within projects
        """
        projects = things.projects()
        if not projects:
            return "No projects found"
    
        formatted_projects = [format_project(project, include_items) for project in projects]
        return "\n\n---\n\n".join(formatted_projects)
  • Tool registration via @mcp.tool decorator on the FastMCP instance 'mcp'.
    @mcp.tool
    async def get_projects(include_items: bool = False) -> str:
  • Helper function that formats a single project dict into a human-readable string, including title, UUID, area, notes, dates, headings, and optionally tasks.
    def format_project(project: dict, include_items: bool = False) -> str:
        """Helper function to format a single project."""
        project_text = f"Title: {project['title']}\nUUID: {project['uuid']}"
    
        if project.get('area'):
            try:
                area = things.get(project['area'])
                if area:
                    project_text += f"\nArea: {area['title']}"
            except Exception:
                pass
    
        if project.get('notes'):
            project_text += f"\nNotes: {project['notes']}"
    
        # Add creation and modification dates
        if project.get('created'):
            project_text += f"\nCreated: {project['created']}"
            # Calculate age since creation
            try:
                age_text = _calculate_age(project['created'])
                project_text += f"\nAge: {age_text}"
            except (ValueError, TypeError):
                pass
    
        if project.get('modified'):
            project_text += f"\nModified: {project['modified']}"
            # Calculate time since last modification
            try:
                modified_age = _calculate_age(project['modified'])
                project_text += f"\nLast modified: {modified_age}"
            except (ValueError, TypeError):
                pass
    
        # Always show headings for projects
        headings = things.tasks(type='heading', project=project['uuid'])
        if headings:
            project_text += "\n\nHeadings:"
            for heading in headings:
                project_text += f"\n- {heading['title']}"
    
        if include_items:
            todos = things.todos(project=project['uuid'])
            if todos:
                project_text += "\n\nTasks:"
                for todo in todos:
                    project_text += f"\n- {todo['title']}"
    
        return project_text
Behavior2/5

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

No annotations are present, so the description must disclose behavioral details. It only states 'Get all projects' without clarifying scope (e.g., whether archived projects are included), potential side effects (none expected for a read tool), or any other constraints.

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 extremely concise, using two sentences with no wasted words. It is front-loaded with the core purpose and the parameter explanation is directly after.

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 has low complexity, a single optional parameter, and an output schema (context signal), the description is somewhat complete. However, it does not mention ordering, filtering, or whether all projects (including those in areas) are returned.

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?

The single parameter 'include_items' is described as 'Include tasks within projects', which adds meaningful context beyond the schema's type and default. The schema description coverage is 0%, but the description compensates adequately for this simple parameter.

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 the tool retrieves all projects from Things, with a specific verb ('Get') and resource ('projects'). It distinguishes itself from sibling tools like 'get_todos' or 'get_areas' by focusing exclusively on projects.

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 such as 'search_items' or other 'get_*' tools. No context about prerequisites or exclusions is given.

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