Skip to main content
Glama
yvanfreitas

MCP Test Server

by yvanfreitas

create_task

Add new tasks to the MCP Test Server by providing a title, optional status, and assigned user ID for task management.

Instructions

Create a new task

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesTask title
statusNoTask statuspending
assignedToNoID of user assigned to this task

Implementation Reference

  • TaskService.create implements the core logic for the create_task tool: destructures input, validates title, generates new task ID, adds to mock data store, and returns success response with new task.
    static create(taskData) {
      const { title, status = 'pending', assignedTo } = taskData;
    
      if (!title) {
        return {
          success: false,
          message: 'Title is required'
        };
      }
    
      const newTask = {
        id: Math.max(...tasks.map(t => t.id)) + 1,
        title,
        status,
        assignedTo: assignedTo || null
      };
    
      tasks.push(newTask);
    
      return {
        success: true,
        message: 'Task created successfully',
        data: newTask
      };
    }
  • Schema definition for create_task tool within taskToolSchemas array, defining input parameters (title required, status with default, assignedTo optional).
    {
      name: 'create_task',
      description: 'Create a new task',
      inputSchema: {
        type: 'object',
        properties: {
          title: {
            type: 'string',
            description: 'Task title'
          },
          status: {
            type: 'string',
            description: 'Task status',
            enum: ['pending', 'in-progress', 'completed'],
            default: 'pending'
          },
          assignedTo: {
            type: 'number',
            description: 'ID of user assigned to this task'
          }
        },
        required: ['title']
      }
    },
  • mcp-server.js:62-63 (registration)
    In the MCP server's CallToolRequestSchema handler, the switch statement registers and dispatches create_task calls to TaskService.create.
    case 'create_task':
      return createMcpResponse(TaskService.create(args));
  • mcp-server.js:39-44 (registration)
    In the ListToolsRequestSchema handler, taskToolSchemas (containing create_task schema) is included in the list of available tools.
    return {
      tools: [
        ...userToolSchemas,
        ...taskToolSchemas,
        searchToolSchema
      ]
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. 'Create a new task' implies a write operation but doesn't specify permissions needed, whether tasks are unique, what happens on duplicate titles, or the response format. It lacks critical behavioral details 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 extremely concise at three words, with zero wasted text. It's front-loaded with the core action, though this brevity comes at the cost of completeness. Every word serves a purpose in stating the tool's function.

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 doesn't explain what a 'task' entails in this system, what the creation response includes, or any side effects. Given the complexity of creating a resource, more context is needed for 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?

The schema description coverage is 100%, with all parameters (title, status, assignedTo) documented in the schema. The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline for high schema coverage without adding value.

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 a new task' clearly states the verb ('create') and resource ('task'), but it's vague about what constitutes a task in this system and doesn't distinguish it from sibling tools like 'create_user' or 'update_task'. It provides basic purpose but lacks specificity about the domain or scope.

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 like 'update_task' or 'get_task', nor does it mention prerequisites or context for task creation. It's a bare statement with no usage context, leaving the agent to infer when this is appropriate.

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/yvanfreitas/MCP-test'

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