Skip to main content
Glama

volkern_complete_task

Mark tasks as completed in Volkern CRM by providing the task ID to update task status and track progress within AI workflows.

Instructions

Mark a task as completed

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskIdYesThe task's unique ID

Implementation Reference

  • Handler implementation for volkern_complete_task tool. Makes a PATCH request to /tasks/{taskId} endpoint with { completada: true } to mark a task as completed.
    case "volkern_complete_task":
      return volkernRequest(`/tasks/${args.taskId}`, "PATCH", { completada: true });
  • Tool schema definition for volkern_complete_task. Defines the tool name, description, and inputSchema requiring a taskId parameter (string type) to identify which task to complete.
    {
      name: "volkern_complete_task",
      description: "Mark a task as completed",
      inputSchema: {
        type: "object",
        properties: {
          taskId: { type: "string", description: "The task's unique ID" }
        },
        required: ["taskId"]
      }
    },
  • src/index.ts:956-958 (registration)
    Server registration of the tools list (including volkern_complete_task) using ListToolsRequestSchema handler.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools };
    });
  • Helper function volkernRequest that handles all API communication. Constructs URLs, adds authentication headers, serializes request bodies, and handles API responses/errors. Used by volkern_complete_task to make the PATCH request.
    async function volkernRequest(
      endpoint: string,
      method: string = "GET",
      body?: Record<string, unknown>
    ): Promise<unknown> {
      const url = `${VOLKERN_API_URL}${endpoint}`;
      
      const options: RequestInit = {
        method,
        headers: {
          "Authorization": `Bearer ${VOLKERN_API_KEY}`,
          "Content-Type": "application/json",
        },
      };
    
      if (body && method !== "GET") {
        options.body = JSON.stringify(body);
      }
    
      const response = await fetch(url, options);
      
      if (!response.ok) {
        const errorData = await response.json().catch(() => ({}));
        throw new Error(
          `Volkern API Error (${response.status}): ${JSON.stringify(errorData)}`
        );
      }
    
      return response.json();
    }
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. 'Mark a task as completed' implies a write/mutation operation but doesn't specify whether this requires special permissions, if the action is reversible, what happens to dependent items, or what confirmation/response to expect. For a mutation tool with zero annotation coverage, this is insufficient behavioral context.

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 extremely concise at just four words, front-loading the essential action without any wasted words. Every word earns its place by conveying the core functionality directly.

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 incomplete. It doesn't address what happens after marking completion (success response, error conditions), whether this affects other system states, or any behavioral nuances. The description alone doesn't provide enough context for confident tool invocation despite the simple parameter schema.

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% with the single parameter 'taskId' well-documented in the schema. The description adds no additional parameter information beyond what's already in the structured schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.

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 'Mark a task as completed' clearly states the action (mark as completed) and resource (task), making the purpose immediately understandable. However, it doesn't differentiate from potential sibling tools like 'volkern_update_task' (if it existed) or explain how this differs from simply updating a task's status field.

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. With sibling tools like 'volkern_list_tasks' and 'volkern_create_task', there's no indication whether this is the primary method for task completion or if tasks should be completed through other means. No prerequisites, constraints, or alternatives are mentioned.

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/DeXpertmx/mcp-volkern'

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