Skip to main content
Glama
mikemc

Todoist MCP Server

by mikemc

todoist_get_section

Retrieve details of a specific section from Todoist using the section ID, enabling efficient task organization and management through the Todoist MCP Server.

Instructions

Get a single section from Todoist

Args: section_id: ID of the section to retrieve

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
section_idYes

Implementation Reference

  • The handler function that executes the core logic of the todoist_get_section tool. It retrieves a specific Todoist section by its ID using the Todoist API client from the context and returns the section data as JSON.
    def todoist_get_section(ctx: Context, section_id: str) -> str:
        """Get a single section from Todoist
    
        Args:
            section_id: ID of the section to retrieve
        """
        todoist_client = ctx.request_context.lifespan_context.todoist_client
    
        try:
            logger.info(f"Getting section with ID: {section_id}")
    
            section = todoist_client.get_section(section_id=section_id)
    
            if not section:
                logger.info(f"No section found with ID: {section_id}")
                return f"No section found with ID: {section_id}"
    
            logger.info(f"Retrieved section: {section.id}")
            return json.dumps(section.to_dict(), indent=2, default=str)
        except Exception as error:
            logger.error(f"Error getting section: {error}")
            return f"Error getting section: {str(error)}"
  • src/main.py:79-79 (registration)
    The registration of the todoist_get_section tool using the FastMCP decorator, which automatically generates the tool schema from the function signature and docstring.
    mcp.tool()(todoist_get_section)
  • src/main.py:19-25 (registration)
    Import statement that brings the todoist_get_section handler into the main.py scope for registration.
    from .sections import (
        todoist_get_sections,
        todoist_get_section,
        todoist_add_section,
        todoist_update_section,
        todoist_delete_section,
    )
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 the basic action ('Get a single section') without mentioning whether this is a read-only operation, what permissions are required, how errors are handled, or what the return format looks like. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 concise with two sentences that directly address the tool's purpose and its single parameter. The structure is front-loaded with the main purpose first, followed by parameter details. There's no wasted text, though the formatting with 'Args:' could be slightly cleaner.

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 tool's moderate complexity (retrieval operation with one parameter), no annotations, no output schema, and 0% schema description coverage, the description is incomplete. It lacks information about return values, error conditions, authentication needs, and how it differs from sibling retrieval tools, making it inadequate for full contextual understanding.

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?

The schema description coverage is 0%, so the description must compensate. It adds the parameter 'section_id' with a brief explanation ('ID of the section to retrieve'), which provides basic semantics beyond the schema's title 'Section Id'. However, with only one parameter documented and no details about format, validation, or examples, it doesn't fully compensate for the lack of schema descriptions.

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 verb 'Get' and the resource 'a single section from Todoist', which is specific and unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'todoist_get_sections' (plural) or 'todoist_get_project', leaving some room for confusion about when to use this versus other retrieval tools.

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 sibling tools like 'todoist_get_sections' for retrieving multiple sections or 'todoist_get_project' for related data, nor does it specify prerequisites or contextual triggers for selecting this specific retrieval method.

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/mikemc/todoist-mcp-server'

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