Skip to main content
Glama

get_inbox_projects

Retrieve the three designated inbox projects from Todoist to organize and manage tasks across personal and shared workspaces.

Instructions

Get the three inbox projects: Inbox, Brian inbox - per Becky, and Becky inbox - per Brian

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The async handler function that executes the 'get_inbox_projects' tool logic. It calls the getInboxProjects service function, formats the result as JSON text content, and handles errors.
    handler: async () => {
      console.error('Executing get_inbox_projects...');
      try {
        const result = await getInboxProjects();
        console.error('get_inbox_projects completed successfully');
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(result, null, 2),
            },
          ],
        };
      } catch (error) {
        throw new Error(
          `Failed to get inbox projects: ${
            error instanceof Error ? error.message : 'Unknown error'
          }`
        );
      }
    },
  • The schema definition for the 'get_inbox_projects' tool, including name, description, and empty input schema (no parameters required).
    schema: {
      name: 'get_inbox_projects',
      description:
        'Get the three inbox projects: Inbox, Brian inbox - per Becky, and Becky inbox - per Brian',
      inputSchema: {
        type: 'object',
        properties: {},
        required: [],
      },
    },
  • Registration of the tool handler in the toolsWithoutArgs registry map, which dispatches tool calls without arguments to the correct handler.
    get_inbox_projects: getInboxProjectsTool.handler,
  • src/index.ts:90-90 (registration)
    The tool schema is registered in the server's ListTools response, making it discoverable by MCP clients.
    getInboxProjectsTool.schema,
  • Helper service function that implements the core logic: lists all projects and filters for inbox projects using isInboxProject utility.
    export async function getInboxProjects(): Promise<ProjectsResponse> {
      try {
        const allProjects = await listProjects();
    
        const filteredProjects = allProjects.projects.filter(isInboxProject);
    
        return {
          projects: filteredProjects,
          total_count: filteredProjects.length,
        };
      } catch (error) {
        throw new Error(`Failed to get inbox projects: ${getErrorMessage(error)}`);
      }
    }
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 states 'Get' which implies a read operation, but doesn't specify if it requires authentication, returns a specific format, has rate limits, or handles errors. 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.

Conciseness5/5

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

The description is a single, efficient sentence that directly states the tool's purpose without any fluff. It's front-loaded with the action and resources, making it easy to parse quickly.

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 simplicity (0 parameters, no annotations, no output schema), the description is adequate but minimal. It specifies what projects are retrieved, which is essential, but lacks details on return format, error handling, or integration context, leaving some gaps for the agent to navigate.

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 tool has 0 parameters, and schema description coverage is 100% (since there are no parameters to describe). The description doesn't need to add parameter semantics, so a baseline of 4 is appropriate as it doesn't have to compensate for any gaps.

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 action ('Get') and the specific resources ('the three inbox projects'), listing them explicitly: Inbox, Brian inbox - per Becky, and Becky inbox - per Brian. It distinguishes from siblings like 'get_becky_shared_projects' or 'get_brian_only_projects' by focusing on inbox projects, though it doesn't explicitly contrast with them.

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 prerequisites, context (e.g., for inbox management vs. other project types), or exclusions, leaving the agent to infer usage from the name and sibling tools alone.

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

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