Skip to main content
Glama

bookmark_task

Idempotent

Star or unstar a task in your private task list to mark priorities for quick personal reference. Provide the task ID and optional bookmarked flag to toggle its state.

Instructions

Star/unstar a task in my own task list (private to me).

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": {
      "task_id": "<task_id>"
    },
    "name": "bookmark_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes
bookmarkedNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true, destructiveHint=false and readOnlyHint=false, so safety and repeatability are covered. The description adds the non-obvious behavioral fact that the bookmark is scoped privately to the caller's own task list, which the schema and annotations do not convey. Return values are covered by the output schema.

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?

A single short sentence with no filler, front-loading the action and then the scope qualifier. Nothing could be removed without losing information.

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

Completeness4/5

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

For a two-parameter toggle with annotations and an output schema in place, the description supplies purpose and the privacy constraint that matter most. The remaining gap is the explicit mapping of the boolean to star versus unstar, which is minor but not zero.

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 description coverage is 0%, so the description must carry parameter meaning. 'Star/unstar' conveys that the boolean controls the on/off direction and that task_id identifies the target, but it never says which value means unstar, whether omitting the boolean defaults to starring, or that task_id must be one of the caller's tasks.

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 concrete verb pair (star/unstar) and resource (task), plus a scope qualifier: 'in my own task list (private to me)'. That scope is meaningful and separates it from any team- or project-level state change, though no sibling is named for contrast.

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 alternation between 'star/unstar' implies the tool is used for toggling a personal bookmark, and the privacy note hints at when this is appropriate. It never states how to reach the unstar path (bookmarked=false) nor any exclusion such as tasks you don't own, so usage is only implied.

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