Skip to main content
Glama

archive-project-task

Archive or unarchive a project task by providing its ID and specifying the desired state. Manage task visibility and organization efficiently.

Instructions

Archive or unarchive a project task

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_task_idYesThe project task ID
archiveYesTrue to archive, false to unarchive

Implementation Reference

  • Primary handler for 'archive-project-task' tool. PATCHes /project_tasks/{id} with active=0 (archive) or active=1 (unarchive) based on the boolean 'archive' param. Returns success message.
    // Archive/Unarchive project task
    export const archiveProjectTask = createTool(
      'archive-project-task',
      'Archive or unarchive a project task',
      z.object({
        project_task_id: z.union([z.string(), z.number()]).describe('The project task ID'),
        archive: z.boolean().describe('True to archive, false to unarchive'),
      }),
      async (params) => {
        const projectTask = await floatApi.patch(
          `/project_tasks/${params.project_task_id}`,
          { active: params.archive ? 0 : 1 },
          projectTaskSchema
        );
        return {
          success: true,
          data: projectTask,
          message: `Project task ${params.archive ? 'archived' : 'unarchived'} successfully`,
        };
      }
    );
  • Input schema for archive-project-task: requires project_task_id (string/number) and archive (boolean to archive or unarchive).
    // Archive/Unarchive project task
    export const archiveProjectTask = createTool(
      'archive-project-task',
      'Archive or unarchive a project task',
      z.object({
        project_task_id: z.union([z.string(), z.number()]).describe('The project task ID'),
        archive: z.boolean().describe('True to archive, false to unarchive'),
      }),
  • Imports archiveProjectTask from project-tasks.ts and registers it in the legacy tools array at line 266.
    import {
      listProjectTasks,
      getProjectTask,
      createProjectTask,
      updateProjectTask,
      deleteProjectTask,
      getProjectTasksByProject,
      getProjectTasksByPhase,
      bulkCreateProjectTasks,
      reorderProjectTasks,
      archiveProjectTask,
      getProjectTaskDependencies,
    } from './project-management/project-tasks.js';
  • Archive-project-task registered as a valid operation in the workflow operation enum for the consolidated manage-project-workflow tool.
    'archive-project-task',
  • Optimized/consolidated handler for archive-project-task within manage-project-workflow. PATCHes /project_tasks/{id} with active: 0 (archive only, no unarchive support in this path).
    case 'archive-project-task':
      return floatApi.patch(`/project_tasks/${id}`, { active: 0 }, projectTaskSchema, format);
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as reversibility, permissions required, or side effects of archiving/unarchiving.

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 clear sentence, concise and front-loaded, but could be slightly expanded without losing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple toggle tool with no output schema or annotations, the description is minimally complete, but lacks behavioral context that would help an agent understand impacts.

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?

With 100% schema description coverage, the description adds no value beyond the schema, simply restating the parameters. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'archive or unarchive' and the resource 'project task', distinguishing it from siblings like create, update, delete.

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 update-project-task or delete-project-task, nor any context on prerequisites or consequences.

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/asachs01/float-mcp'

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