Skip to main content
Glama

doer_reorder_pinned

Set the display order of pinned todo lists in the Doer sidebar by passing an ordered array of todo list IDs.

Instructions

Update the sequential ordering position of pinned todo lists in the Doer sidebar

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": {
      "todo_list_ids": "<todo_list_ids>"
    },
    "name": "doer_reorder_pinned"
  }
}

Input Schema

NameRequiredDescriptionDefault
todo_list_idsYesOrdered list of pinned todo list IDs representing the new sequence

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It does not say whether the array replaces the entire pinned ordering or only part of it, what happens to pinned lists omitted from the array, whether ordering persists across sessions, or what errors occur if an unpinned or unknown ID is supplied.

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

Conciseness4/5

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

A single front-loaded sentence with no filler or redundancy. It is efficiently sized, though its brevity is partly the source of the missing behavioral detail.

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

Completeness2/5

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

For a mutation tool with no annotations and no output schema, the description should clarify full-replacement semantics and preconditions on pinned state. Neither is present, leaving the agent likely to call it with a partial ID list and produce unintended ordering.

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

Parameters2/5

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

Schema coverage is 100% and the one parameter is documented as an 'Ordered list of pinned todo list IDs representing the new sequence'. The description adds only the phrase 'sequential ordering position', which is weaker than the schema's 'new sequence' and does not clarify that all pinned IDs must typically be included.

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 states a specific verb and resource: 'Update the sequential ordering position of pinned todo lists in the Doer sidebar'. This distinguishes it implicitly from pin/unpin (doer_toggle_pin) and general list edits (doer_update_todo_list) by scoping it to ordering of already-pinned lists.

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?

It gives no when-to-use or when-not-to-use guidance, no statement that the affected lists must already be pinned, and no routing to sibling tools such as doer_toggle_pin for pinning. The agent must infer the calling context entirely.

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