Skip to main content
Glama

get_becky_shared_projects

Retrieve projects owned by Becky that are shared for handling tasks in her designated scope per Brian's instructions.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'get_becky_shared_projects' tool. It executes the core service function, formats the response as MCP content, and handles errors.
    handler: async () => {
      console.error('Executing get_becky_shared_projects...');
      try {
        const result = await getBeckySharedProjects();
        console.error('get_becky_shared_projects completed successfully');
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(result, null, 2),
            },
          ],
        };
      } catch (error) {
        throw new Error(
          `Failed to get Becky shared projects: ${
            error instanceof Error ? error.message : 'Unknown error'
          }`
        );
      }
    },
  • Schema definition for the tool, specifying name, description, and empty input schema (no parameters required).
    schema: {
      name: 'get_becky_shared_projects',
      description:
        'Get projects that belong to Becky and are shared for tasks in her ballpark to handle per Brian',
      inputSchema: {
        type: 'object',
        properties: {},
        required: [],
      },
    },
  • Registration of the tool handler in the toolsWithoutArgs registry, mapping 'get_becky_shared_projects' to getBeckySharedProjectsTool.handler.
    get_becky_shared_projects: getBeckySharedProjectsTool.handler,
  • Helper function implementing the core logic: fetches all projects and filters those that are Becky shared using isBeckySharedProject utility.
    export async function getBeckySharedProjects(): Promise<ProjectsResponse> {
      try {
        const allProjects = await listProjects();
    
        const filteredProjects = allProjects.projects.filter(isBeckySharedProject);
    
        return {
          projects: filteredProjects,
          total_count: filteredProjects.length,
        };
      } catch (error) {
        throw new Error(
          `Failed to get Becky shared projects: ${getErrorMessage(error)}`
        );
      }
    }
  • src/index.ts:89-89 (registration)
    The tool schema is included in the list of tools returned by ListToolsRequestHandler.
    getBeckySharedProjectsTool.schema,
Behavior2/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 of behavioral disclosure. It mentions 'Get projects', suggesting a read-only operation, but doesn't specify if this requires authentication, what the return format looks like, or any rate limits. The description lacks details on behavioral traits like pagination, error handling, or data freshness, which are critical for a tool with zero annotation coverage.

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 conveys the core purpose, but it's somewhat wordy and ambiguous with phrases like 'ballpark' and 'per Brian'. It could be more front-loaded and precise. While not excessively long, it doesn't maximize clarity per word, and the structure could be improved for better readability.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., project details, list format) or any behavioral aspects like error conditions. For a tool with no structured data to rely on, the description should provide more context about the operation and results, but it falls short, leaving significant gaps for the 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 tool has 0 parameters, and schema description coverage is 100%, so there are no parameters to document. The description doesn't need to compensate for any gaps, and it appropriately doesn't discuss parameters. A baseline of 4 is applied since no parameter information is required, and the description doesn't add unnecessary details.

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 Becky that are shared for tasks in her domain, which provides a basic purpose. However, it's somewhat vague about what 'ballpark' and 'per Brian' mean operationally, and it doesn't clearly differentiate from sibling tools like 'get_brian_shared_projects' or 'list_gtd_projects' in terms of scope or filtering criteria.

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 for Becky's shared projects but offers no explicit guidance on when to use this tool versus alternatives like 'get_brian_shared_projects' or 'list_gtd_projects'. There's no mention of prerequisites, exclusions, or specific contexts where this tool is preferred, leaving the agent to infer usage from the description 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