Skip to main content
Glama

Niche of One Network

Set my reading position

reader_set_position

Members. Set where you are in a book (percent), synced to OneReader on every device. The newest position wins. Shows a preview first; call again with confirm true to save.

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": {
      "book": "<book>",
      "percent": "<percent>"
    },
    "name": "reader_set_position"
  }
}

Input Schema

NameRequiredDescriptionDefault
bookYesBook title or id, as reader_library lists it.
confirmNoLeave out to preview. true writes it.
percentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare that this is a non-read-only, non-destructive, non-idempotent write; the description adds the two-step preview-then-commit workflow, cross-device sync behavior, and the 'newest position wins' conflict rule. These are substantive behaviors an agent could not infer from the annotations alone. Minor tension with idempotentHint=false (repeating the same percent converges to the same state) but not a contradiction.

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?

Three short sentences with no filler, and the preview/confirm instruction — the most actionable detail — comes last but is easy to find. The leading fragment 'Members.' is a stray scope tag that adds a beat of ambiguity without 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 3-parameter write tool with no output schema, the description covers the mutation semantics, the confirmation flow, and conflict resolution, which is most of what an agent needs to call it correctly. It leaves unstated what a preview response looks like or what errors occur on an invalid book, but those are secondary.

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?

Two of three parameters are already described in the schema (book via reader_library, confirm as the write flag), so coverage is 67%. The description only adds the word 'percent' to clarify the units of the undescribed numeric parameter — marginal added meaning beyond the schema's 0-100 bounds. Baseline 3 fits.

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 — set a reading position in a book, expressed as a percent — which is unambiguous about what the tool does. It doesn't name or contrast any sibling, but the operation is distinctive enough that confusion with reader_library or reader_note_save is unlikely.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit call-sequence guidance: the first call previews, and you must call again with confirm=true to actually write. That is more useful than generic when-to-use prose. It stops short of stating when this tool should be preferred over, say, taking a note, but no close alternative exists in the sibling list.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources