Skip to main content
Glama

server_update_task

Modify scheduled tasks for Minecraft servers to adjust automation settings and server management routines.

Instructions

Update an existing scheduled task for a Minecraft server

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
server_idYesServer ID or UUID
task_idYesTask ID to update
updatesYesTask fields to update

Implementation Reference

  • The MCP tool 'server_update_task' is registered and implemented in this handler. It updates a task using a PATCH request to the Crafty API.
    server.tool(
      "server_update_task",
      "Update an existing scheduled task for a Minecraft server",
      {
        server_id: z.string().describe("Server ID or UUID"),
        task_id: z.string().describe("Task ID to update"),
        updates: z.record(z.string(), z.unknown()).describe("Task fields to update"),
      },
      async ({ server_id, task_id, updates }) => {
        try {
          const data = await client.patch(
            `/servers/${server_id}/tasks/${task_id}`,
            updates
          );
          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 full burden for behavioral disclosure. It states this is an update operation but doesn't cover critical aspects like required permissions, whether changes are reversible, rate limits, or what happens to unspecified task fields. This is inadequate for a mutation tool.

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 directly states the tool's purpose without unnecessary words. It's appropriately front-loaded and wastes no space, making it easy to parse quickly.

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 mutation tool with no annotations and no output schema, the description is insufficient. It lacks behavioral details (e.g., error conditions, response format), usage context, and doesn't compensate for the absence of structured safety or output information, leaving significant gaps.

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 parameters are documented in the schema. The description adds no additional semantic context beyond implying 'updates' modifies task fields, which the schema already covers. This meets the baseline for high schema coverage.

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 ('Update') and resource ('existing scheduled task for a Minecraft server'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'server_update' or 'server_update_backup_config', which prevents a perfect score.

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 comparisons to siblings like 'server_create_task' or 'server_delete_task', leaving usage context unclear.

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