Skip to main content
Glama
Sign In
upsprint-mcp

upsprint-mcp

by Pedro-Roger
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Mover task (webhook)

move_task

Move a task to a different column on the board. Specify the task and target column; the current column is detected automatically.

Instructions

Move uma task para outra coluna do board (action moveTask). A coluna atual é detectada automaticamente.

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>",
      "to_column_id": "<to_column_id>"
    },
    "name": "move_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYesUUID da task
positionNoPosição na coluna
to_column_idYesUUID da coluna de destino

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It adds that the current column is detected automatically, which is useful, but does not disclose permissions, side effects, or potential errors. The description is minimal 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 consists of two short sentences that directly convey the tool's purpose and key behavior. No wasted words, and the core action is front-loaded.

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

Completeness3/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 3 parameters, the description covers the main functionality but lacks information about return values, error handling, or any side effects. Adequate but not thorough.

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 each parameter. The description adds context by explaining the absence of a 'from_column' parameter due to automatic detection, which adds value. Scores baseline 3.

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 tool moves a task to another column and mentions the action name 'moveTask'. It is specific about the resource and action, but does not explicitly differentiate from sibling tools like 'move_task_and_update', so a slight deduction.

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 like 'move_task_and_update' or 'assign_task'. It neither states prerequisites nor exclusions.

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