Skip to main content
Glama
dragosroua

addTaskManager MCP Server

by dragosroua

assess_archive_project_to_collection

Archive a project to a collection in the addTaskManager app to organize completed work and maintain a clear task management system.

Instructions

Archive a project to a collection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectRecordNameYesRecord name of the project
collectionRecordNameYesRecord name of the collection

Implementation Reference

  • src/index.ts:414-423 (registration)
    Tool registration including name, description, and input schema definition.
    name: 'assess_archive_project_to_collection',
    description: 'Archive a project to a collection.',
    inputSchema: {
      type: 'object',
      properties: {
        projectRecordName: { type: 'string', description: 'Record name of the project' },
        collectionRecordName: { type: 'string', description: 'Record name of the collection' }
      },
      required: ['projectRecordName', 'collectionRecordName']
    }
  • The core handler function that executes the tool. Currently a mock implementation returning a success message; in production, it would interact with CloudKitService to update project references.
    private async archiveProjectToCollection(projectRecordName: string, collectionRecordName: string) {
      // Mock archiving project to collection via CloudKit
      return { content: [{ type: 'text', text: `Project ${projectRecordName} archived to collection ${collectionRecordName}` }] };
  • src/index.ts:698-700 (registration)
    Dispatch handler in the switch statement that routes tool calls to the archiveProjectToCollection method.
    case 'assess_archive_project_to_collection':
      this.validateArgs(args, ['projectRecordName', 'collectionRecordName']);
      return await this.archiveProjectToCollection(args.projectRecordName, args.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 of behavioral disclosure. 'Archive' implies a state change (likely making the project inactive or moving it to archival storage), but the description doesn't specify whether this is reversible, what permissions are required, whether it affects associated tasks, or what happens to the project's data. For a mutation tool with zero annotation coverage, this is a significant gap in behavioral context.

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 wasted words. It's front-loaded with the core action and resources, making it immediately understandable. Every word earns its place by conveying essential information about 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?

Given that this is a mutation tool (implied by 'Archive') with no annotations and no output schema, the description is incomplete. It doesn't address behavioral aspects like reversibility, side effects, or error conditions, nor does it explain what the tool returns. For a tool that modifies data, this lack of context leaves significant gaps for an AI agent to understand its full impact.

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 clearly documented in the schema itself ('projectRecordName' and 'collectionRecordName'). The description adds no additional parameter semantics beyond what's in the schema—it doesn't explain what constitutes a valid record name, format requirements, or relationship constraints. With high schema coverage, the baseline score of 3 is appropriate as the 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 ('Archive') and target resources ('a project to a collection'), providing a specific verb+resource combination. It distinguishes from some siblings like 'assess_create_project' or 'assess_edit_project' by focusing on archiving rather than creation or modification. However, it doesn't explicitly differentiate from the closely related 'assess_archive_task_to_collection' tool, which archives tasks instead of projects.

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. There is no mention of prerequisites (e.g., existing project and collection), when archiving is appropriate versus deletion or other status changes, or how this differs from similar tools like 'assess_archive_task_to_collection' or 'decide_move_project_to_do'. The agent must infer usage from the tool name alone.

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