Skip to main content
Glama
dragosroua

addTaskManager MCP Server

by dragosroua

assess_archive_task_to_collection

Archive a task to a collection in the addTaskManager app to organize completed or inactive items within the Assess phase of the ADD framework.

Instructions

Archive a task to a collection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskRecordNameYesRecord name of the task
collectionRecordNameYesRecord name of the collection

Implementation Reference

  • src/index.ts:695-697 (registration)
    Tool registration in the CallToolRequestSchema switch statement, dispatching to the handler method.
    case 'assess_archive_task_to_collection':
      this.validateArgs(args, ['taskRecordName', 'collectionRecordName']);
      return await this.archiveTaskToCollection(args.taskRecordName, args.collectionRecordName);
  • src/index.ts:402-412 (registration)
    Tool registration in ListToolsRequestSchema including name, description, and input schema.
      name: 'assess_archive_task_to_collection',
      description: 'Archive a task to a collection.',
      inputSchema: {
        type: 'object',
        properties: {
          taskRecordName: { type: 'string', description: 'Record name of the task' },
          collectionRecordName: { type: 'string', description: 'Record name of the collection' }
        },
        required: ['taskRecordName', 'collectionRecordName']
      }
    },
  • The main handler function implementing the tool logic. Currently a mock that returns a success message; in production would interact with CloudKitService.
    private async archiveTaskToCollection(taskRecordName: string, collectionRecordName: string) {
      // Mock archiving task to collection via CloudKit
      return { content: [{ type: 'text', text: `Task ${taskRecordName} archived to collection ${collectionRecordName}` }] };
    }
  • Input schema definition for the tool, specifying required parameters and types.
    inputSchema: {
      type: 'object',
      properties: {
        taskRecordName: { type: 'string', description: 'Record name of the task' },
        collectionRecordName: { type: 'string', description: 'Record name of the collection' }
      },
      required: ['taskRecordName', 'collectionRecordName']
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. 'Archive' implies a mutation (likely moving or marking a task), but it doesn't disclose if this is reversible, requires specific permissions, affects task status, or has side effects (e.g., removing from other lists). The description lacks behavioral details beyond the basic action.

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 front-loaded with the core action and resources, making it easy to parse quickly. No unnecessary words or redundancy are present.

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 no annotations and no output schema, the description is incomplete for a mutation tool. It doesn't explain what 'archive' entails behaviorally, what the result looks like, or potential errors. For a tool that likely changes state, more context is needed to use it 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%, with both parameters ('taskRecordName', 'collectionRecordName') clearly documented in the schema. The description adds no additional meaning about parameters beyond implying they are required for the archive operation. Baseline 3 is appropriate since the schema does the heavy lifting.

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 'Archive a task to a collection' clearly states the action (archive) and target resources (task, collection), but it's vague about what 'archive' means operationally. It distinguishes from obvious siblings like 'assess_create_task' or 'assess_edit_task', but doesn't clarify how it differs from similar tools like 'assess_add_task_to_idea' or 'assess_archive_project_to_collection' in terms of purpose.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't specify if this is for completed tasks, how it relates to 'assess_add_task_to_idea/project', or what happens if a task is already archived. The description only states what it does, not when it's 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/dragosroua/addtaskmanager-mcp-server'

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