Skip to main content
Glama
Sign In
Tendem MCP

Tendem MCP

by Toloka
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

cancel_task

Cancel a pending Tendem task to stop processing. Use before approval to avoid cost charges.

Instructions

Cancel a Tendem task. Costs are not refunded after approval.

Can be called at any time. Note: costs are not refunded if cancelled after approval.

Args: task_id: The Tendem task ID (UUID) to cancel.

Returns: Confirmation message.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "task_id": "<task_id>"
    },
    "name": "cancel_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description must cover behavioral traits. It warns that costs are not refunded after approval, which is critical. However, it does not disclose other side effects like state changes, reversibility, or permissions needed.

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 concise, with a clear first sentence stating the action and key warning. It then indicates usage timing and provides structured args/returns. No unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has one parameter and no output schema, the description covers the main points: action, cost caveat, parameter, and return type. It lacks details about edge cases (e.g., already cancelled) but is sufficient for standard use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description adds meaningful information by specifying the parameter as 'Tendem task ID (UUID)' and stating its purpose ('to cancel'). This compensates for the lack of schema-level descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action 'Cancel' and the resource 'Tendem task'. It differentiates from sibling tools like approve_task and create_task by specifying the cancel operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description states 'Can be called at any time,' giving a usage context, but does not explicitly say when to avoid using it or compare to alternatives. The cost warning implies caution after approval, but no direct guidance about alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools