Skip to main content
Glama

server_run_task

Manually trigger a scheduled task immediately on a server. Use this tool to run tasks without waiting for their scheduled time.

Instructions

Manually trigger a scheduled task immediately

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
server_idYesServer ID or UUID
task_idYesTask ID to run

Implementation Reference

  • The tool 'server_run_task' is registered and implemented within 'registerServerTaskTools' in 'src/tools/server-tasks.ts'. The handler makes a POST request to the Crafty API to trigger the task.
    server.tool(
      "server_run_task",
      "Manually trigger a scheduled task immediately",
      {
        server_id: z.string().describe("Server ID or UUID"),
        task_id: z.string().describe("Task ID to run"),
      },
      async ({ server_id, task_id }) => {
        try {
          const data = await client.post(
            `/servers/${server_id}/tasks/${task_id}/run`
          );
          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, the description carries full burden but provides minimal behavioral insight. It implies a write operation ('trigger') but doesn't disclose permissions needed, side effects (e.g., task execution, logs), rate limits, or what happens if the task fails. 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 with no wasted words. It front-loads the core action ('manually trigger') and key constraint ('immediately'), making it easy to parse.

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 details on behavior (e.g., success/failure responses, execution context), error handling, and integration with sibling tools, leaving significant gaps for an agent to use it correctly.

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 the schema already documents both parameters (server_id, task_id). The description adds no additional meaning about parameters beyond implying they identify the task to run, meeting 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 ('manually trigger') and resource ('a scheduled task'), specifying it happens 'immediately'. It distinguishes from sibling tools like server_create_task (creates) and server_get_task (reads), but doesn't explicitly differentiate from server_update_task (which might modify rather than trigger).

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 on when to use this tool versus alternatives is provided. The description doesn't mention prerequisites (e.g., the task must exist, be scheduled), nor does it contrast with similar tools like server_update_task or server_send_command for immediate actions.

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