Skip to main content
Glama

AgileHero

by io.agilehero
OverviewDiscussionsAdmin

move_retro_item

Move a retrospective item: regroup a note on a new-model retrospective where the workspace has them, move a card to another column of a classic retrospective board otherwise. New model, Group stage only: topic_id puts the note into that topic (group of notes); column (title or uid) makes it a topic of its own there, at position among the column's topics (omit for last). Pass expected_updated_at, the note's topic updated_at from get_retrospective, to be refused with code stale when someone regrouped it meanwhile. Outside Group the call is refused with code wrong_stage and the current stage; kudos and other notes never mix. Classic boards take column and position only (position omitted = top). Requires a Pro or trial workspace.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe note uid (classic boards: the item uid) from get_retrospective
columnNoTarget column title or uid
positionNoIndex in the target column (0 = first)
topic_idNoTarget topic uid; leave column out
expected_updated_atNoThe note's topic updated_at as last read (conflict check)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / column / description
      Previous value: -"Target column name or uid"New value: +"Target column title or uid"
    • addedInput schema / properties / expected_updated_at
      Added value: +{
+  "description": "The note's topic updated_at as last read (conflict check)",
+  "type": "string"
+}
    • changedInput schema / properties / id / description
      Previous value: -"The retro item uid (from get_retrospective)"New value: +"The note uid (classic boards: the item uid) from get_retrospective"
    • changedInput schema / properties / position / description
      Previous value: -"Position in the target column; omit for the top"New value: +"Index in the target column (0 = first)"
    • addedInput schema / properties / topic_id
      Added value: +{
+  "description": "Target topic uid; leave column out",
+  "minLength": 1,
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "id",
-  "column"
-]New value: +[
+  "id"
+]
  2. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  3. First observed

TDQS

A5/5.0
Behavior5/5

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

Beyond the non-destructive mutation annotations, the description discloses stage restrictions, stale-conflict refusal via expected_updated_at, mixed-content restrictions, model-specific parameter behavior, and workspace prerequisite. These are exactly the behavioral constraints an agent needs before calling.

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 dense but front-loaded and earns its length through conditional model behavior, error semantics, and parameter interactions. Every sentence carries operational information without filler.

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 complex mutation tool with no output schema, the description covers the two operating modes, required prerequisites, conflict handling, stage restrictions, and parameter behavior. It is complete enough for an agent to call it correctly without external context.

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

Parameters5/5

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

Although schema coverage is 100%, the description adds substantial meaning: it explains topic_id as grouping into a topic, column as creating a topic at a position, expected_updated_at as a concurrency guard, and how parameters differ for classic versus new-model boards. This goes well beyond the schema text.

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 gives a specific verb and resource, 'Move a retrospective item', and immediately distinguishes the two supported retrospective models. An agent can tell this is not a generic card move but a retro-item regrouping/column-move operation.

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 exactly when each behavior applies: new-model retrospectives use topic_id/column grouping only in Group stage, while classic boards use column and position. It also gives refusal conditions (wrong_stage, stale) and the Pro/trial prerequisite, leaving little to inference.

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

All AgileHero toolsInspect
Try in Browser
Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources