Skip to main content
Glama

list_brian_inbox_per_becky_tasks

Retrieve Brian's Todoist inbox tasks assigned to Becky with structured task details including priority, due dates, and completion status.

Instructions

List all Brian inbox per Becky tasks from Todoist using the ##Brian inbox - per Becky filter. Returns structured JSON data with task details including id, content, description, completion status, labels, priority, due date, and comment count.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Defines the MCP tool 'list_brian_inbox_per_becky_tasks' including its schema and handler function. The handler calls the service function listBrianInboxPerBeckyTasks and returns the result as formatted JSON text.
    export const listBrianInboxPerBeckyTasksTool: Tool = {
      schema: {
        name: 'list_brian_inbox_per_becky_tasks',
        description:
          'List all Brian inbox per Becky tasks from Todoist using the ##Brian inbox - per Becky filter. Returns structured JSON data with task details including id, content, description, completion status, labels, priority, due date, and comment count.',
        inputSchema: {
          type: 'object',
          properties: {},
          required: [],
        },
      },
      handler: async () => {
        console.error('Executing list_brian_inbox_per_becky_tasks...');
        const result = await listBrianInboxPerBeckyTasks();
        console.error('list_brian_inbox_per_becky_tasks completed successfully');
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(result, null, 2),
            },
          ],
        };
      },
    };
  • Input/output schema definition for the tool, no input parameters required.
    schema: {
      name: 'list_brian_inbox_per_becky_tasks',
      description:
        'List all Brian inbox per Becky tasks from Todoist using the ##Brian inbox - per Becky filter. Returns structured JSON data with task details including id, content, description, completion status, labels, priority, due date, and comment count.',
      inputSchema: {
        type: 'object',
        properties: {},
        required: [],
      },
    },
  • Registers the tool name to its handler function in the toolsWithoutArgs registry for dispatching tool calls.
    list_brian_inbox_per_becky_tasks: listBrianInboxPerBeckyTasksTool.handler,
  • Core service function that retrieves tasks from Todoist API using the specific project filter for 'Brian inbox - per Becky' excluding subtasks.
    export async function listBrianInboxPerBeckyTasks(): Promise<TasksResponse> {
      return await fetchTasksByFilter(
        `##${ProjectNames.BRIAN_INBOX_PER_BECKY} & !subtask`,
        'list Brian inbox per Becky tasks'
      );
    }
  • src/index.ts:84-84 (registration)
    Registers the tool schema in the MCP server's listTools response.
    listBrianInboxPerBeckyTasksTool.schema,
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the return format ('structured JSON data') and details included (id, content, etc.), which is valuable. However, it doesn't mention behavioral aspects like pagination, rate limits, authentication needs, or error handling. For a read-only list tool with zero annotation coverage, this is adequate but leaves gaps.

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, well-structured sentence that efficiently conveys purpose, usage, and output details without any wasted words. It is front-loaded with the core action and resource, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 output schema, no annotations), the description is reasonably complete. It explains what the tool does, when to use it, and what it returns. However, without annotations or output schema, it could benefit from more behavioral context (e.g., pagination, errors). For a straightforward list tool, it's largely sufficient.

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 with 100% schema description coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate. A baseline of 4 is assigned as it compensates adequately for the lack of parameters by focusing on output semantics.

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 specific action ('List all Brian inbox per Becky tasks'), identifies the resource (Todoist tasks), and distinguishes from siblings by specifying the exact filter used ('##Brian inbox - per Becky filter'). It explicitly differentiates from tools like 'list_becky_inbox_per_brian_tasks' and other task-listing tools by its unique scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states when to use this tool: for listing tasks from the '##Brian inbox - per Becky filter' in Todoist. It implicitly distinguishes from alternatives like 'list_becky_inbox_per_brian_tasks' (different filter) and 'get_tasks_due_today' (different scope), though it doesn't name them directly. The specificity of the filter provides clear contextual boundaries.

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