Skip to main content
Glama
Sign In
Tendem MCP

Tendem MCP

by Toloka
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_tasks

Retrieve a paginated list of Tendem tasks, showing each task's current status.

Instructions

List all Tendem tasks with their statuses.

Args: page_number: Page number (0-indexed). page_size: Number of results per page (1-100).

Returns: Paginated list of Tendem tasks.

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": {
      "page_number": "<page_number>",
      "page_size": "<page_size>"
    },
    "name": "list_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_numberYes
page_sizeYes

Output Schema

NameRequiredDescriptionDefault
tasksYes
totalYes
page_numberYes
page_sizeYes
pagesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.8/5.0
Behavior3/5

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

No annotations provided, so the description carries the burden. It discloses pagination behavior via page_number and page_size, but lacks details on auth, rate limits, or data freshness. Adequate for a simple read operation.

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?

Very concise, using a clear structured format (Args, Returns). Every sentence adds value with no wasted 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?

With an output schema present, the description need not detail return values. It mentions 'Paginated list of Tendem tasks', which is sufficient. Could specify ordering or filtering but not essential for a list tool.

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 explains parameters: 'Page number (0-indexed)' and 'Number of results per page (1-100)'. This adds meaning beyond the schema types.

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 'List all Tendem tasks with their statuses', using a specific verb and resource. It distinguishes itself from sibling tools like get_task (single task) and create_task (creation).

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 such as get_task or get_all_task_results. The description does not mention any exclusions or context for selection.

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