Skip to main content
Glama

save_position

Stores a media file's playback position in seconds so playback can resume from the same point later.

Instructions

Save playback position for a file (for resume playback)

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": {
      "path": "<path>",
      "position": "<position>"
    },
    "name": "save_position"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPath to the media file
positionYesPosition in seconds

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It indicates a state mutation by using 'Save' but does not explain persistence semantics, overwrite behavior, validation of position, or what happens if the path is invalid. For a mutation tool with zero annotations, this is a significant gap.

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?

The description is a single, front-loaded sentence with no unnecessary wording. The parenthetical is short and directly supports the purpose.

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 simple two-parameter tool with a fully described schema, the description is minimally adequate. It explains the overall goal but omits behavioral details that matter for a mutation tool, especially since no annotations or output schema are available.

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 100%, so the schema already documents both parameters clearly. The description adds no meaning beyond the schema, such as position units or path constraints. Baseline 3 is appropriate when the schema does the heavy lifting.

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: save playback position for a file. The parenthetical clarifies the intent as resume playback. It is clear, though it does not explicitly differentiate itself from siblings such as resume or get_position.

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 phrase '(for resume playback)' gives implied context for why the tool is used. However, it does not state when to call it versus alternatives like resume or get_position, nor does it specify prerequisites such as having an active playback session.

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