Skip to main content
Glama
yvanfreitas

MCP Test Server

by yvanfreitas

update_task

Modify existing task details including title, status, and assigned user to manage workflow changes effectively.

Instructions

Update an existing task

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTask ID
titleNoTask title
statusNoTask status
assignedToNoID of user assigned to this task

Implementation Reference

  • Input schema and description for the 'update_task' tool, defining parameters like id (required), title, status, assignedTo.
    {
      name: 'update_task',
      description: 'Update an existing task',
      inputSchema: {
        type: 'object',
        properties: {
          id: {
            type: 'number',
            description: 'Task ID'
          },
          title: {
            type: 'string',
            description: 'Task title'
          },
          status: {
            type: 'string',
            description: 'Task status',
            enum: ['pending', 'in-progress', 'completed']
          },
          assignedTo: {
            type: 'number',
            description: 'ID of user assigned to this task'
          }
        },
        required: ['id']
      }
    }
  • mcp-server.js:38-46 (registration)
    Tool list registration handler that includes 'update_task' schema by spreading taskToolSchemas into the list of available tools.
    this.server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: [
          ...userToolSchemas,
          ...taskToolSchemas,
          searchToolSchema
        ]
      };
    });
  • TaskService.update static method implements the business logic for updating a task by ID in the mock data store, handling partial updates.
    static update(id, taskData) {
      const taskIndex = tasks.findIndex(t => t.id === id);
      
      if (taskIndex === -1) {
        return {
          success: false,
          message: 'Task not found'
        };
      }
    
      const { title, status, assignedTo } = taskData;
      const updatedTask = { ...tasks[taskIndex] };
    
      if (title) updatedTask.title = title;
      if (status) updatedTask.status = status;
      if (assignedTo !== undefined) updatedTask.assignedTo = assignedTo ? parseInt(assignedTo) : null;
    
      tasks[taskIndex] = updatedTask;
    
      return {
        success: true,
        message: 'Task updated successfully',
        data: updatedTask
      };
    }
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 'update' implies mutation but fails to disclose critical traits like required permissions, whether updates are reversible, error handling, or rate limits. This is a significant gap 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 'Update an existing task' is a single, efficient sentence with zero waste. It's appropriately sized and front-loaded, making it easy to parse without unnecessary details.

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 tool's complexity as a mutation tool with no annotations and no output schema, the description is incomplete. It lacks behavioral context, usage guidelines, and details on what happens post-update, making it inadequate for safe and effective use by an AI agent.

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 fully documents all 4 parameters (id, title, status, assignedTo) with descriptions and enum for status. The description adds no additional meaning beyond what the schema provides, meeting the baseline for high coverage.

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 'Update an existing task' clearly states the verb ('update') and resource ('task'), but it's vague about what aspects can be updated and doesn't distinguish it from potential sibling tools like 'create_task' or 'get_task'. It meets the basic requirement 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?

The description provides no guidance on when to use this tool versus alternatives such as 'create_task' for new tasks or 'get_task' for viewing. There's no mention of prerequisites, context, or exclusions, leaving usage entirely implied from the tool name.

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