Skip to main content
Glama

get_brian_only_projects

Retrieve Todoist projects owned exclusively by Brian that are not shared with other users.

Instructions

Get projects that belong only to Brian and are NOT shared

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Full tool definition for 'get_brian_only_projects' including inline schema and the handler function that calls the core getBrianOnlyProjects service and formats the response as JSON text content.
    export const getBrianOnlyProjectsTool: Tool = {
      schema: {
        name: 'get_brian_only_projects',
        description: 'Get projects that belong only to Brian and are NOT shared',
        inputSchema: {
          type: 'object',
          properties: {},
          required: [],
        },
      },
      handler: async () => {
        console.error('Executing get_brian_only_projects...');
        try {
          const result = await getBrianOnlyProjects();
          console.error('get_brian_only_projects completed successfully');
          return {
            content: [
              {
                type: 'text',
                text: JSON.stringify(result, null, 2),
              },
            ],
          };
        } catch (error) {
          throw new Error(
            `Failed to get Brian-only projects: ${
              error instanceof Error ? error.message : 'Unknown error'
            }`
          );
        }
      },
    };
  • Core helper function that lists all projects, filters for Brian-only projects using isBrianOnlyProject predicate, and returns structured ProjectsResponse.
    export async function getBrianOnlyProjects(): Promise<ProjectsResponse> {
      try {
        const allProjects = await listProjects();
    
        const filteredProjects = allProjects.projects.filter(isBrianOnlyProject);
    
        return {
          projects: filteredProjects,
          total_count: filteredProjects.length,
        };
      } catch (error) {
        throw new Error(
          `Failed to get Brian-only projects: ${getErrorMessage(error)}`
        );
      }
    }
  • Registers the handler for 'get_brian_only_projects' (and other no-arg tools) in the toolsWithoutArgs map used by handleToolRequest.
    const toolsWithoutArgs: Record<string, () => Promise<ToolResponse>> = {
      list_personal_inbox_tasks: listPersonalInboxTasksTool.handler,
      list_brian_inbox_per_becky_tasks: listBrianInboxPerBeckyTasksTool.handler,
      list_becky_inbox_per_brian_tasks: listBeckyInboxPerBrianTasksTool.handler,
      list_next_actions: listNextActionsTool.handler,
      get_brian_only_projects: getBrianOnlyProjectsTool.handler,
      get_brian_shared_projects: getBrianSharedProjectsTool.handler,
      get_becky_shared_projects: getBeckySharedProjectsTool.handler,
      get_inbox_projects: getInboxProjectsTool.handler,
      get_context_labels: getContextLabelsTool.handler,
      get_chores_due_today: getChoresDueTodayTool.handler,
      get_tasks_due_tomorrow: getTasksDueTomorrowTool.handler,
      get_tasks_due_this_week: getTasksDueThisWeekTool.handler,
      get_tickler_tasks: getTicklerTasksTool.handler,
      list_gtd_projects: listGtdProjectsTool.handler,
      get_waiting_tasks: getWaitingTasksTool.handler,
      get_recent_media: getRecentMediaTool.handler,
      get_areas_of_focus: getAreasOfFocusTool.handler,
      get_shopping_list: getShoppingListTool.handler,
      list_brian_time_sensitive_tasks: listBrianTimeSensitiveTasksTool.handler,
      list_becky_time_sensitive_tasks: listBeckyTimeSensitiveTasksTool.handler,
    };
  • Imports the getBrianOnlyProjectsTool for use in registration.
    getBrianOnlyProjectsTool,
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 indicates a read operation ('Get') but doesn't specify return format, pagination, error conditions, or any behavioral traits like rate limits or authentication needs. For a tool with zero annotation coverage, this leaves significant gaps in understanding how it behaves beyond the basic purpose.

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 wasted words. It's front-loaded with the core action and immediately specifies the key constraints ('only to Brian' and 'NOT shared'), making it highly concise and well-structured for quick understanding.

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 output schema, no annotations), the description is adequate for conveying the basic purpose. However, it lacks details on return values, error handling, or behavioral context, which could be important for an AI agent to use it correctly. It's minimally viable but leaves room for more completeness in a real-world scenario.

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 input schema has 0 parameters with 100% coverage, so no parameters are documented in the schema. The description doesn't need to add parameter details, and it appropriately focuses on the tool's purpose without unnecessary parameter explanations. This meets the baseline for tools with no parameters, as there's nothing to compensate for.

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 projects') and specifies the resource scope ('that belong only to Brian and are NOT shared'), which distinguishes it from general project retrieval tools. However, it doesn't explicitly differentiate from sibling tools like 'get_brian_shared_projects' or 'list_gtd_projects' beyond the 'only Brian' and 'NOT shared' qualifiers, making it clear but not fully sibling-differentiated.

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

Usage Guidelines3/5

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

The description implies usage context by specifying 'only to Brian and are NOT shared', suggesting it's for retrieving Brian's private projects. However, it lacks explicit guidance on when to use this tool versus alternatives like 'get_brian_shared_projects' or 'list_gtd_projects', and provides no exclusions or prerequisites, leaving usage somewhat inferred rather than clearly defined.

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