Skip to main content
Glama

Cherry Notes

by app.cherrynotes
OverviewDiscussionsAdmin

cherry_pick

Idempotent

Claims items for work. This is STEP 1 — ALWAYS pick before doing any work. NEVER do work without calling this first. Requires idempotency_key. Pass item_numbers from the display (e.g. [3] for item 3), or set pick_all=true to pick all todo items. Show the display field to the user verbatim in a code block.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_idsNoAlternative to item_numbers — UUIDs from structuredContent. Most agents should use item_numbers instead.
pick_allNoIf true, pick all todo items in the current project. When set, item_numbers and item_ids are ignored.
item_textsNoDisplay only — the text of each item being cherry-picked, for human-readable permission prompts. Ignored by the server.
item_numbersNoThe item NUMBERS to cherry-pick, as shown in the display from get_items. This is what the user means when they say "work on item 3". Preferred over item_ids.
idempotency_keyYesA unique string for this cherry-pick request. Reusing the same key with the same items returns the same result (idempotent).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pickedYes
displayYesPre-formatted confirmation. Show this to the user verbatim in a code block.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / display
      Added value: +{
+  "description": "Pre-formatted confirmation. Show this to the user verbatim in a code block.",
+  "type": "string"
+}
    • changedOutput schema / required
      Previous value: -[
-  "picked"
-]New value: +[
+  "picked",
+  "display"
+]
  2. Changed2 schema fields changed
    • removedOutput schema / properties / display
      Removed value: -{
-  "description": "Pre-formatted display text for this response.",
-  "type": "string"
-}
    • changedOutput schema / required
      Previous value: -[
-  "picked",
-  "display"
-]New value: +[
+  "picked"
+]
  3. Changed1 schema field changed
    • changedOutput schema / properties / display / description
      Previous value: -"Pre-formatted confirmation. Show this to the user verbatim in a code block."New value: +"Pre-formatted display text for this response."
  4. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish idempotency and non-read-only/non-destructive behavior. The description adds workflow-critical context beyond annotations: this is a mandatory precondition for other work and the agent must present the display field verbatim to the user. It stops short of describing the exact server-side effect of claiming items, but that is largely covered by annotations.

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?

The description is compact and imperative, with the most important workflow constraint front-loaded. It earns most of its sentences, though 'Requires idempotency_key' and the item_numbers/pick_all instruction duplicate schema information rather than adding new content.

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 tool with an output schema and full parameter documentation, the description covers everything needed to call it correctly: workflow position, required key, selection modes, and the mandatory user-facing display of the output. No critical invocation detail is missing.

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 each parameter has a rich description, so the baseline is 3. The description adds a useful example ('[3] for item 3') and highlights pick_all as an alternative, but it mostly restates what the schema already conveys about item_numbers, item_ids, and pick_all.

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 opens with a specific verb and resource ('Claims items for work') and immediately anchors the tool in the workflow ('STEP 1 — ALWAYS pick before doing any work'). This makes it unmistakable relative to siblings like cherry_unpick, complete_items, and get_items, even without naming them.

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?

Usage is explicitly prescribed: 'ALWAYS pick before doing any work' and 'NEVER do work without calling this first.' It also gives concrete selection guidance (item_numbers from display, or pick_all=true) and notes the required idempotency_key, leaving no ambiguity about when and how to call it.

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

All Cherry Notes 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