Skip to main content
Glama
dragosroua

addTaskManager MCP Server

by dragosroua

assess_edit_task

Edit task content in the Assess realm, including updating task names and priority levels from 1 to 5.

Instructions

Edit task content in Assess realm (taskName, priority).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskRecordNameYesRecord name of the task to edit
taskNameNoUpdated task name/description
taskPriorityNoUpdated task priority (1-5)

Implementation Reference

  • The main handler function for the 'assess_edit_task' tool. It constructs a success message indicating updates to task name and/or priority. Currently implemented as a mock without actual CloudKit database operations.
    private async editTask(taskRecordName: string, taskName?: string, taskPriority?: number) {
      // Mock fetch & check realm (should be REALM_ASSESS_ID)
      // Mock update: console.log('Mock CloudKit: Editing Task', taskRecordName, { taskName, taskPriority });
      let updateMsg = `Task ${taskRecordName} updated.`;
      if (taskName) updateMsg += ` Name set to "${taskName}".`;
      if (taskPriority) updateMsg += ` Priority set to ${taskPriority}.`;
      return { content: [{ type: 'text', text: updateMsg }] };
    }
  • Input schema definition for the 'assess_edit_task' tool, specifying parameters: taskRecordName (required), taskName, and taskPriority (1-5). Part of the tool registration in ListToolsRequestSchema.
      name: 'assess_edit_task',
      description: 'Edit task content in Assess realm (taskName, priority).',
      inputSchema: {
        type: 'object',
        properties: {
          taskRecordName: { type: 'string', description: 'Record name of the task to edit' },
          taskName: { type: 'string', description: 'Updated task name/description' },
          taskPriority: { type: 'integer', minimum: 1, maximum: 5, description: 'Updated task priority (1-5)'},
        },
        required: ['taskRecordName']
      }
    },
  • src/index.ts:663-665 (registration)
    Tool dispatch/registration in the CallToolRequestSchema switch statement. Validates required args and calls the editTask handler.
      this.validateArgs(args, ['taskRecordName']);
      return await this.editTask(args.taskRecordName, args.taskName, args.taskPriority);
    case 'assess_create_project':
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states it's an edit operation, implying mutation, but doesn't cover critical aspects like required permissions, whether changes are reversible, error handling (e.g., if the task doesn't exist), or response format. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 that front-loads the core action ('Edit task content') and includes key details (realm and fields). There's no wasted verbiage, but it could be slightly more structured (e.g., separating purpose from usage). Overall, it's appropriately concise for the tool's complexity.

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 (a mutation operation with 3 parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't address behavioral aspects like side effects, error cases, or return values, which are crucial for safe invocation. While the schema covers parameters well, the overall context for using this tool effectively is insufficient.

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 (taskRecordName, taskName, taskPriority) with descriptions and constraints. The description adds minimal value by listing 'taskName, priority' as editable fields, but doesn't provide additional semantics beyond what the schema specifies. Baseline 3 is appropriate when schema does the heavy lifting.

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 ('Edit task content') and specifies the resource ('task') and realm ('Assess'), along with the editable fields ('taskName, priority'). It distinguishes from siblings like 'assess_create_task' (creation vs. editing) and 'assess_archive_task_to_collection' (editing vs. archiving), though it doesn't explicitly contrast them. The purpose is specific but could be more detailed on 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. It doesn't mention prerequisites (e.g., that the task must exist), exclusions, or comparisons to siblings like 'assess_edit_idea' or 'assess_edit_project'. Usage is implied by the action 'edit,' but no explicit context or decision criteria are given.

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/dragosroua/addtaskmanager-mcp-server'

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