Skip to main content
Glama

doer_toggle_pin

Toggles a todo list's pinned status in the Doer persistent sidebar so you can keep key lists visible or remove them from the pinned area.

Instructions

Toggle the pinned status of a todo list on the Doer persistent 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": {
      "id": "<id>"
    },
    "name": "doer_toggle_pin"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesUnique identifier of the todo list whose pin status to toggle

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It adds the useful detail that the pin appears on the 'persistent sidebar', but never says whether the call returns the new state, whether it requires prior read of the current state (a toggle is not idempotent), or what happens if the item is already in the target state.

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?

One sentence, front-loaded with the action, with no filler. The trailing sidebar phrase is short and contextually useful rather than padding.

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 one-parameter mutation tool with a fully described schema and no output schema, this is close to adequate, but the non-idempotent nature of a toggle and the absence of any return-value statement are gaps an agent would want closed.

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 coverage is 100% and the single 'id' parameter is fully documented in the schema, so the baseline of 3 applies. The description adds no format, constraint, or sourcing detail beyond restating that the id identifies the list whose pin is flipped.

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?

States a specific verb and resource ('toggle the pinned status of a todo list'), which is enough to separate it from doer_toggle_todo_item and doer_reorder_pinned. It stops short of naming the siblings explicitly, but the resource framing is clear.

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?

The action is unambiguous enough that usage is implied: call it to flip pin state. There is no explicit when-to-use, no when-not, and no routing to doer_reorder_pinned for ordering pinned items, so guidance is only implicit.

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