Skip to main content
Glama
ainote-dev

AI Note MCP Server

by ainote-dev

update_task

Modify an existing task's details, including content, importance, or completion status, using the task ID to ensure accurate updates in AI Note MCP Server.

Instructions

Update an existing task

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
completed_atNoMark as completed (ISO format) or null to uncomplete
contentNoNew task content
idYesTask ID
is_importantNoUpdate important status

Implementation Reference

  • Handler function for the 'update_task' tool. It forwards the arguments to apiClient.callTool('update_task') and returns the result.
    handler: async (args, { apiClient }) => {
      const result = await apiClient.callTool('update_task', args);
      return result;  // Return full result with { content: [...] }
    }
  • Tool definition function returning the name, description, and inputSchema for 'update_task'.
    function updateTaskDefinition() {
      return {
        name: 'update_task',
        description: 'Update an existing task',
        inputSchema: {
          type: 'object',
          properties: {
            id: {
              type: 'string',
              description: 'Task ID'
            },
            content: {
              type: 'string',
              description: 'New task content'
            },
            is_important: {
              type: 'boolean',
              description: 'Update important status'
            },
            completed_at: {
              type: 'string',
              description: 'Mark as completed (ISO format) or null to uncomplete'
            }
          },
          required: ['id']
        }
      };
    }
  • Registration of the 'update_task' tool within the getSharedTools() array, combining its definition and handler.
    {
      definition: updateTaskDefinition(),
      handler: async (args, { apiClient }) => {
        const result = await apiClient.callTool('update_task', args);
        return result;  // Return full result with { content: [...] }
      }
    },
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. While 'Update' implies a mutation operation, it doesn't specify what permissions are required, whether changes are reversible, or what happens if the task doesn't exist. For a mutation tool with zero annotation coverage, this leaves significant behavioral questions unanswered.

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 that communicates the core purpose without any wasted words. It's appropriately sized for a simple update operation and gets straight to the point.

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 4 parameters, no annotations, and no output schema, the description is insufficient. It doesn't address what the tool returns, error conditions, or behavioral nuances. Given the complexity of an update operation and the lack of structured metadata, the description should provide more complete context.

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%, meaning all parameters are documented in the input schema. The description doesn't add any additional parameter semantics beyond what's already in the schema, so it meets the baseline expectation but doesn't provide extra value.

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 clearly states the action ('Update') and resource ('an existing task'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'create_task' beyond the 'existing' qualifier, which is why it doesn't reach a perfect score of 5.

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 'create_task' or 'delete_task'. There's no mention of prerequisites, error conditions, or specific contexts where this tool is preferred over others in the sibling set.

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/ainote-dev/ainote-mcp'

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