Skip to main content
Glama
emmron
by emmron

mcp__gemini__create_project_tasks

Automate project task creation by converting requirements into actionable tasks tailored to project type and complexity. Streamline planning and execution with this AI-powered tool.

Instructions

Create project tasks from requirements

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
complexityNoComplexity levelmedium
project_typeNoProject typegeneral
requirementsYesProject requirements

Implementation Reference

  • Complete registration of the 'mcp__gemini__create_project_tasks' tool, including input schema, description, and the full inline handler function that generates tasks using AI and persists to storage.
        this.registerTool(
          'mcp__gemini__create_project_tasks',
          'Create project tasks from requirements',
          {
            requirements: { type: 'string', description: 'Project requirements', required: true },
            project_type: { type: 'string', description: 'Project type', default: 'general' },
            complexity: { type: 'string', description: 'Complexity level', default: 'medium' }
          },
          async (args) => {
            const { requirements, project_type = 'general', complexity = 'medium' } = args;
            validateString(requirements, 'requirements');
            
            const prompt = `Break down these project requirements into specific, actionable tasks:
    
    ${requirements}
    
    Project Type: ${project_type}
    Complexity: ${complexity}
    
    Create a structured task list with:
    1. Clear task descriptions
    2. Priority levels (high/medium/low)
    3. Estimated effort
    4. Dependencies between tasks
    5. Implementation order`;
    
            const taskBreakdown = await aiClient.call(prompt, 'main', { complexity });
            
            // Save to storage
            const taskData = await storage.read('tasks');
            const timestamp = new Date().toISOString();
            taskData.last_requirements = requirements;
            taskData.last_breakdown = taskBreakdown;
            taskData.updated = timestamp;
            await storage.write('tasks', taskData);
            
            return `📋 **Project Tasks Created**\\n\\n${taskBreakdown}`;
          }
        );
  • The core handler function for 'mcp__gemini__create_project_tasks' that destructures args, validates input, constructs an AI prompt, calls aiClient to generate task breakdown, persists data to storage, and returns formatted response.
          async (args) => {
            const { requirements, project_type = 'general', complexity = 'medium' } = args;
            validateString(requirements, 'requirements');
            
            const prompt = `Break down these project requirements into specific, actionable tasks:
    
    ${requirements}
    
    Project Type: ${project_type}
    Complexity: ${complexity}
    
    Create a structured task list with:
    1. Clear task descriptions
    2. Priority levels (high/medium/low)
    3. Estimated effort
    4. Dependencies between tasks
    5. Implementation order`;
    
            const taskBreakdown = await aiClient.call(prompt, 'main', { complexity });
            
            // Save to storage
            const taskData = await storage.read('tasks');
            const timestamp = new Date().toISOString();
            taskData.last_requirements = requirements;
            taskData.last_breakdown = taskBreakdown;
            taskData.updated = timestamp;
            await storage.write('tasks', taskData);
            
            return `📋 **Project Tasks Created**\\n\\n${taskBreakdown}`;
          }
  • Input schema parameters for the tool defining requirements (required string), project_type, and complexity.
    {
      requirements: { type: 'string', description: 'Project requirements', required: true },
      project_type: { type: 'string', description: 'Project type', default: 'general' },
      complexity: { type: 'string', description: 'Complexity level', default: 'medium' }
    },
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'create' which implies a write/mutation operation, but doesn't disclose behavioral traits like permissions needed, whether tasks are saved permanently, rate limits, or what the output looks like. For a creation tool with zero annotation coverage, this is a significant gap in transparency.

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

Conciseness4/5

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

The description is a single, efficient sentence with no wasted words. It's appropriately sized for a tool with three parameters and gets straight to the point. However, it could be more front-loaded with additional context, but as-is it's concise.

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 creation tool with behavioral implications, the description is incomplete. It doesn't explain what 'create' entails operationally, what format the tasks are in, or any error conditions. For a tool that likely generates structured output from requirements, more context is needed to guide effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all three parameters with descriptions. The description adds no additional meaning about parameters beyond implying that 'requirements' input leads to task creation. With high schema coverage, the baseline is 3 even without param info in the description.

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 'Create project tasks from requirements' states a clear verb ('create') and resource ('project tasks'), but it's vague about what 'project tasks' are and how they're generated. It doesn't distinguish from sibling tools like 'planner_pro' or 'team_orchestrator' which might have overlapping functionality. The purpose is understandable but lacks specificity.

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?

No guidance is provided on when to use this tool versus alternatives. With many sibling tools focused on planning, analysis, and generation, there's no indication of this tool's specific context or prerequisites. The description implies usage for task creation from requirements, but offers no explicit when/when-not instructions or named alternatives.

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

Related 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/emmron/gemini-mcp'

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