Skip to main content
Glama

get_brian_shared_projects

Retrieve Brian's shared Todoist projects for task delegation to Becky, enabling efficient team collaboration on assigned responsibilities.

Instructions

Get projects that belong to Brian and are shared for tasks in his ballpark to handle per Becky

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Defines the MCP Tool for 'get_brian_shared_projects' including its schema (no inputs) and handler. The handler calls the getBrianSharedProjects service, stringifies the result to JSON, and returns it as text content. Catches and rethrows errors.
    export const getBrianSharedProjectsTool: Tool = {
      schema: {
        name: 'get_brian_shared_projects',
        description:
          'Get projects that belong to Brian and are shared for tasks in his ballpark to handle per Becky',
        inputSchema: {
          type: 'object',
          properties: {},
          required: [],
        },
      },
      handler: async () => {
        console.error('Executing get_brian_shared_projects...');
        try {
          const result = await getBrianSharedProjects();
          console.error('get_brian_shared_projects completed successfully');
          return {
            content: [
              {
                type: 'text',
                text: JSON.stringify(result, null, 2),
              },
            ],
          };
        } catch (error) {
          throw new Error(
            `Failed to get Brian shared projects: ${
              error instanceof Error ? error.message : 'Unknown error'
            }`
          );
        }
      },
    };
  • Input/output schema definition for the 'get_brian_shared_projects' tool: no required inputs, returns structured projects data.
    schema: {
      name: 'get_brian_shared_projects',
      description:
        'Get projects that belong to Brian and are shared for tasks in his ballpark to handle per Becky',
      inputSchema: {
        type: 'object',
        properties: {},
        required: [],
      },
    },
  • Core helper function that lists all Todoist projects and filters them to those that are Brian shared projects using the isBrianSharedProject utility function.
    export async function getBrianSharedProjects(): Promise<ProjectsResponse> {
      try {
        const allProjects = await listProjects();
    
        const filteredProjects = allProjects.projects.filter(isBrianSharedProject);
    
        return {
          projects: filteredProjects,
          total_count: filteredProjects.length,
        };
      } catch (error) {
        throw new Error(
          `Failed to get Brian shared projects: ${getErrorMessage(error)}`
        );
      }
    }
  • Registers the tool handler in the dispatch map for tools without arguments in the central tool request handler.
    get_brian_shared_projects: getBrianSharedProjectsTool.handler,
  • src/index.ts:88-88 (registration)
    Registers the tool schema in the listTools response for MCP server discovery.
    getBrianSharedProjectsTool.schema,
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 mentions 'Get projects' which suggests a read operation, but doesn't specify if it's safe, requires permissions, has rate limits, or what the return format might be. The description adds minimal context beyond the basic action, failing to compensate for the lack of annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is a single sentence that is somewhat wordy and unclear ('in his ballpark to handle per Becky'), which could be more concise. It front-loads the purpose but includes ambiguous phrasing that doesn't earn its place efficiently. It's not overly verbose but lacks polish.

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 no annotations, no output schema, and a simple tool with 0 parameters, the description is incomplete. It fails to explain what 'shared projects' means, how they are returned, or any behavioral traits. For a tool with no structured data, the description should provide more context to be fully helpful to an agent.

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 parameter documentation is needed. The description doesn't add parameter information, which is appropriate here. Baseline is 4 for 0 parameters, as the schema fully covers the absence of inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool retrieves projects belonging to Brian that are shared for tasks in his ballpark, which provides a vague purpose. However, it lacks specificity about what 'ballpark' means or what 'shared for tasks' entails, making it somewhat ambiguous. It distinguishes from siblings like 'get_brian_only_projects' by mentioning 'shared' but doesn't clearly differentiate from 'get_becky_shared_projects' beyond the name.

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 implies usage when needing Brian's shared projects for tasks in his ballpark, but provides no explicit guidance on when to use this tool versus alternatives like 'get_brian_only_projects' or 'get_becky_shared_projects'. There are no exclusions, prerequisites, or clear context for selection, leaving the agent to infer usage based on the vague description.

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