Skip to main content
Glama

bookmark_goto

Jump to a saved bookmark by ID: resumes playback at its position if the file is playing, otherwise opens the file there. Refuses bookmarks on discs not in the drive.

Instructions

Jump to a bookmark by id. Seeks if its file is already playing; otherwise opens that file at the bookmarked position, saving a resume point for the outgoing one. A bookmark on a disc is refused, without loading anything, when that disc is not the one in the drive.

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": "bookmark_goto"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesBookmark id from bookmark_list

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it discloses the two execution paths, the side effect of saving a resume point for the outgoing file, and a refusal condition (bookmark on a disc not in the drive, refused without loading anything). It stops short of covering invalid/unknown ids or whether playback begins after opening.

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?

Three short sentences, front-loaded with the action, then the two branches, then the edge-case refusal. Every sentence contributes distinct information with no filler.

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 one-parameter navigation tool with no annotations and no output schema, the description covers the action, the branching behavior, side effects, and one failure mode, which is enough to call it correctly. Remaining gaps are minor: error behavior for a stale or unknown id is not mentioned.

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 parameter already documents that the id comes from bookmark_list. The description adds only "by id", which is no more than the schema states, so baseline 3 applies.

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?

States a specific verb and resource ("Jump to a bookmark by id") and immediately distinguishes itself by describing the state-dependent behavior: seeks if the file is playing, otherwise opens the file. An agent can tell this apart from siblings like bookmark_list or resume without opening any schema.

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?

Usage is implied rather than stated: the tool is the 'go to this bookmark' action, and the schema points to bookmark_list as the id source. There is no explicit when-not guidance or named alternative (e.g., using resume for non-bookmark positions), so the agent must infer selection criteria.

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

Deploy Server

Other Tools