Skip to main content
Glama

delete-task

Delete a task or allocation from float.com by providing its task ID to remove it from the schedule.

Instructions

Delete a task/allocation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYesThe task ID (task_id)

Implementation Reference

  • Handler function for the 'delete-task' tool. Calls floatApi.delete to send a DELETE request to /tasks/{task_id}, then returns a success message.
    // Delete task
    export const deleteTask = createTool(
      'delete-task',
      'Delete a task/allocation',
      z.object({
        task_id: z.union([z.string(), z.number()]).describe('The task ID (task_id)'),
      }),
      async (params) => {
        await floatApi.delete(`/tasks/${params.task_id}`);
        return { success: true, message: 'Task deleted successfully' };
      }
    );
  • Input schema for the delete-task tool: expects a single 'task_id' parameter that can be a string or number.
    z.object({
      task_id: z.union([z.string(), z.number()]).describe('The task ID (task_id)'),
    }),
  • The floatApi.delete method used by the delete-task handler to make the actual HTTP DELETE request to the Float API.
    async delete<T>(url: string, schema?: z.ZodType<T>, format: ResponseFormat = 'json'): Promise<T> {
      return this.handleRateLimitRetry(() =>
        this.makeRequest<T>('DELETE', url, undefined, schema, format)
      );
    }
  • Registration of deleteTask in the legacyTools array, making it available as part of the MCP server tools.
    deleteTask,
  • Import of deleteTask from the tasks.ts module into the tools index for registration.
      deleteTask,
    } from './project-management/tasks.js';
Behavior2/5

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

No annotations are present, so the description must cover behavior. It only states the action without any details about consequences (e.g., cascading effects, irreversibility, required permissions). This is insufficient for a destructive operation.

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 very concise, using only 4 words. However, this brevity sacrifices completeness, so while it is efficient, it is not well-structured for clarity.

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 destructive nature and lack of annotations or output schema, the description should provide more context (e.g., effects, error conditions, typical use cases). It is too brief to be considered complete.

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 input schema already documents the single parameter 'task_id' with 100% coverage. The description adds no additional meaning, so it meets the baseline but does not enhance understanding beyond the schema.

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 states 'Delete a task/allocation', which identifies the verb and resource, but it ambiguously groups two resources with a slash. This could confuse whether it deletes tasks, allocations, or both. Sibling tool 'delete-allocation' exists, but description does not differentiate, so purpose is only moderately clear.

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 sibling delete tools (e.g., delete-allocation, delete-project-task). There is no mention of prerequisites, context, or alternatives, leaving the agent to infer usage.

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