Skip to main content
Glama
Sign In

Lion Reader

by com.lionreader
OverviewDiscussionsAdmin

set_collection_positions

Idempotent

Set the order of articles in a collection (e.g. a book's chapters): a list sorted by position (list_entries with the collection's subscriptionId and sortBy: position) shows lower positions first, then articles without one. Pass exactly one of entryIds or positions; articles you don't name keep their positions, so clear stale ones with null. Articles must already be in the collection (add_to_collection). Returns the IDs whose position changed and those not in the collection. Fails with a not-found error if the collection isn't the user's.

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": {
      "collectionId": "<collectionId>"
    },
    "name": "set_collection_positions"
  }
}

Input Schema

NameRequiredDescriptionDefault
entryIdsNoEntry IDs in order: they get positions 1, 2, 3, …
positionsNoEntries and their positions, to move a few without renumbering the rest
collectionIdYesThe collection's subscription ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare idempotent, non-destructive, non-read-only, so the safety profile is covered; the description goes further by disclosing the partial-update semantics ('articles you don't name keep their positions'), the return content (changed IDs plus IDs not in the collection), and the failure mode (not-found error if the collection isn't the user's). That is behavior an agent cannot infer from the annotations or schema.

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?

Dense but well front-loaded: the operation is stated first, then mechanics, then return/error behavior. Every clause carries information, though the opening sentence is long enough that the core constraint ('exactly one of entryIds or positions') arrives slightly buried.

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?

With no output schema, the description correctly takes on the job of describing return values (IDs whose position changed, IDs not in the collection) and error behavior. For a 3-parameter mutation with a partially-overwriting semantic, nothing an agent needs to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema already explains entryIds ordering and null-clears-position, so the baseline is 3. The description earns extra credit for stating the exclusivity constraint between entryIds and positions and for explaining the read-back pattern (list_entries with subscriptionId and sortBy: position), neither of which is expressible in the schema.

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: 'Set the order of articles in a collection', with a concrete example (book chapters). It is immediately distinguishable from siblings like add_to_collection, which the description references only as a prerequisite.

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?

Explicitly names the two mutually exclusive modes ('Pass exactly one of entryIds or positions') and states a prerequisite ('Articles must already be in the collection (add_to_collection)'). It also gives the escape hatch for stale data ('clear stale ones with null'), so an agent knows both when to use this tool and how to select a mode.

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

All Lion Reader toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources