Skip to main content
Glama

task_create

Create new tasks with titles, project assignments, and due dates to organize developer workflows within AI Ops Hub's task management system.

Instructions

Создать новую задачу

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesЗаголовок задачи
projectNoПроект
dueNoСрок выполнения (YYYY-MM-DD)

Implementation Reference

  • Core handler function that implements the task_create tool logic: loads existing tasks from markdown file, generates new task with ID, persists the updated list, and returns the new task.
    async createTask(title: string, project?: string, due?: string): Promise<Task> {
      try {
        console.log(`✅ Создание задачи: ${title}`);
        
        const tasks = await this.loadTasks();
        
        const newTask: Task = {
          id: this.getNextId(tasks),
          title,
          project,
          due,
          created_at: new Date().toISOString(),
        };
        
        tasks.push(newTask);
        await this.saveTasks(tasks);
        
        console.log(`✅ Задача создана: ${title} (ID: ${newTask.id})`);
        
        return newTask;
      } catch (error) {
        console.error('Ошибка создания задачи:', error);
        throw new Error(`Ошибка создания задачи: ${error}`);
      }
    }
  • Input schema definition for the task_create tool in the stdio MCP server's listTools response.
      name: 'task_create',
      description: 'Создать новую задачу',
      inputSchema: {
        type: 'object',
        properties: {
          title: {
            type: 'string',
            description: 'Заголовок задачи',
          },
          project: {
            type: 'string',
            description: 'Проект',
          },
          due: {
            type: 'string',
            description: 'Срок выполнения (YYYY-MM-DD)',
          },
        },
        required: ['title'],
      },
    },
  • Dispatch handler in stdio MCP server's CallToolRequestSchema that invokes TaskService.createTask for task_create tool calls.
    case 'task_create':
      return {
        content: await this.taskService.createTask(args.title as string, args.project as string, args.due as string)
      };
  • TypeScript interface defining the structure of Task objects used and returned by the task_create handler.
    export interface Task {
      id: number;
      title: string;
      project?: string;
      due?: string;
      created_at: string;
      completed_at?: string;
    }
  • Dispatch handler in HTTP transport's /call endpoint that invokes TaskService.createTask for task_create tool calls.
    case 'task_create':
      result = await this.taskService.createTask(args.title, args.project, args.due);
      break;
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 states the action ('create') but doesn't cover permissions needed, whether the task is saved permanently, error conditions, or response format. This leaves significant gaps for a mutation tool.

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 with zero waste. It's appropriately sized and front-loaded, directly stating the tool's purpose without unnecessary elaboration.

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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral traits (e.g., side effects, permissions), response format, and error handling, which are critical for an agent to use this tool effectively.

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 (title, project, due) with descriptions. The description adds no additional parameter semantics beyond what's in the schema, resulting in the baseline score for high coverage.

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 'Создать новую задачу' (Create a new task) clearly states the verb ('create') and resource ('task'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'task_list' beyond the basic action, which prevents a perfect score.

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 provides no guidance on when to use this tool versus alternatives. There's no mention of prerequisites, when not to use it, or how it relates to sibling tools like 'task_list' or 'file_write', leaving the agent without contextual usage cues.

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/Galiusbro/MCP'

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