Skip to main content
Glama
competlab

competlab-mcp-server

by competlab

move_ticket

Move a ticket between columns or reorder it within a column. Specify destination status and position or neighbouring ticket IDs to place it precisely.

Instructions

Move a ticket to another column, or reorder it inside the one it is in. Name the destination column in status, then where it goes: position='top' or 'bottom', or the two tickets it will sit between — beforeId directly ABOVE it, afterId directly BELOW; either or both. A position and a neighbour together are refused. Omitting everything puts it at the bottom — the opposite of a new ticket, which lands at the top. A neighbour that has been deleted, or now sits in another column, is not used; if you named both and the one below now sits above the one above, the one above is kept; if neither can be used, the ticket goes to the bottom. A move never fails because your view was a moment old. The answer says where it landed: placement.above and placement.below are its neighbours now; placement.ignored names each neighbour you named that was not used and why (other_column usually means you read it off another column's list). An empty ignored means every named neighbour was used, not that nothing sits between them: compare above and below with what you named, and if they differ and the place matters, re-read that column in board order (sort='board', status=) — the only read to take neighbours from — and move again. What the columns mean: triage — nobody has decided yet; todo — decided and not started; in_progress — being worked on; done — finished; dismissed — the team decided not to do it. The set is fixed and a project cannot add to it. Needs a read_write API key; a read key is refused and can only list and read.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusYesThe column the ticket ends up in — always the destination, even when it is the column it already sits in
afterIdNoThe ticket that will sit directly BELOW this one — its ID, or its number: '#14'
beforeIdNoThe ticket that will sit directly ABOVE this one — its ID, or its number: '#14'
positionNoThe top or the bottom of the destination column, without reading it first. Name a position OR neighbours, not both
ticketIdYesThe ticket's ID from list_tickets, or its number as a person writes it: '#14'
projectIdYesProject ID (from list_projects)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv4.0.1

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false and openWorldHint=false; the description adds substantial behavioral context the annotations cannot convey: conflict resolution when both neighbours are named, deletion/moved-neighbour handling, the optimistic-view guarantee ('A move never fails because your view was a moment old'), and the return shape via placement.above/below/ignored. No output schema exists, so disclosing the response structure here is essential and it is done well.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded and the ordering is logical, but at roughly 400 words it is heavily padded: the full enumeration of the five fixed columns, the parenthetical about other_column, and the re-read advice on sort='board' are verbose for a description. Much of the conflict-resolution content earns its place; the column glossary and trailing guidance do not.

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

Completeness5/5

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

For a 6-parameter mutation tool with no output schema, this covers what an agent needs: destination semantics, the two placement mechanisms, default behavior, failure/conflict rules, auth requirements, and the response fields to inspect. Nothing material is left for the agent to infer.

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 coverage is 100%, so the baseline is 3, but the description genuinely adds semantics: beforeId is defined as sitting directly ABOVE and afterId directly BELOW (orientation an agent can easily invert), position vs neighbour is declared exclusive, and omitting everything means bottom — the inverse of create_ticket. It stops short of adding format details beyond the schema's '#14' pattern.

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 first sentence states a specific verb+resource with two distinct modes: 'Move a ticket to another column, or reorder it inside the one it is in.' That cleanly separates it from update_ticket and the other ticket siblings without requiring the schema to be opened.

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

Usage Guidelines5/5

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

It states explicitly how to choose between mechanisms ('Name the destination column in status, then where it goes'), names the mutually exclusive case ('A position and a neighbour together are refused'), gives the default when nothing is specified, and states the auth requirement ('Needs a read_write API key; a read key is refused'). This is unusually complete routing guidance.

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