Skip to main content
Glama
Sign In
productive-mcp-rb2

productive-mcp-rb2

by rubenlangeweg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

move_task_to_list

move_task_to_list
Idempotent

Move a task from a source task list to a target task list within the same project by specifying the task ID and target list ID.

Instructions

Move a task to a different task list within the same project

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>",
      "task_list_id": "<task_list_id>"
    },
    "name": "move_task_to_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYesID of the task to move
task_list_idYesID of the task list to move the task to

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0-alpha.7

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already provide safety profile (idempotent, non-destructive). Description adds the constraint 'within the same project', but lacks details on positioning, subtask handling, or reversibility.

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?

Single focused sentence, 12 words, front-loaded with verb. 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?

For a simple move operation with no output schema, the description is adequately complete. Could mention error conditions or position behavior, but not necessary for basic 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 covers both parameters with descriptions. Description adds the crucial constraint that both IDs must belong to the same project, adding meaning beyond the schema.

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 (move) and resource (task) to a different list within the same project. It is specific but does not differentiate from siblings like reposition_task or update_task_list.

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?

Implied usage when moving a task between lists, but no explicit guidance on when not to use or alternatives. Agent must infer from context.

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