Skip to main content
Glama

server_delete_task

Remove scheduled tasks from Minecraft servers to manage automation and free up resources.

Instructions

Delete a scheduled task from a Minecraft server

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
server_idYesServer ID or UUID
task_idYesTask ID to delete

Implementation Reference

  • The handler for the 'server_delete_task' tool is defined as part of the registerServerTaskTools function. It uses the client to perform a DELETE request to the server's task endpoint.
    server.tool(
      "server_delete_task",
      "Delete a scheduled task from a Minecraft server",
      {
        server_id: z.string().describe("Server ID or UUID"),
        task_id: z.string().describe("Task ID to delete"),
      },
      async ({ server_id, task_id }) => {
        try {
          const data = await client.delete(`/servers/${server_id}/tasks/${task_id}`);
          return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
        } catch (error) {
          const msg = error instanceof Error ? error.message : String(error);
          return { content: [{ type: "text", text: `Error: ${msg}` }], isError: true };
        }
      }
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool performs a deletion operation but doesn't mention critical behavioral aspects: whether this action is reversible, what permissions are required, if it's destructive to server operations, or what happens on success/failure. For a mutation tool with zero annotation coverage, this is a significant gap.

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 that communicates the core purpose without unnecessary words. It's appropriately sized for a simple deletion operation and front-loads the essential information.

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?

For a destructive mutation tool with no annotations and no output schema, the description is inadequate. It doesn't explain what happens after deletion (success response, error conditions), doesn't mention dependencies or side effects, and provides no behavioral context. The description should do more given the tool's complexity and lack of structured metadata.

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 both parameters are fully documented in the schema. The description doesn't add any additional semantic context about the parameters beyond what's already in the schema (server_id and task_id). This meets the baseline expectation when schema coverage is complete.

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 ('Delete') and target resource ('a scheduled task from a Minecraft server'), which is specific and unambiguous. However, it doesn't differentiate from sibling tools like 'server_delete', 'server_delete_backup', or 'server_delete_file', which all perform deletion operations on different server resources.

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., needing an existing task), exclusions, or relationships to sibling tools like 'server_get_task' (to verify existence) or 'server_list_tasks' (to find task IDs).

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/HadiCherkaoui/crafty-mcp'

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