Skip to main content
Glama
Sign In

Lion Reader

by com.lionreader
OverviewDiscussionsAdmin

set_entry_scores

Idempotent

Set or clear (null) numeric scores on up to 1000 entries, to prioritize the user's reading: lists sorted by score (list_entries sortBy: score) show higher scores first, then unscored entries. A score is the user's, so it applies in every list the entry is in. Overwrites any previous score; idempotent. Returns the entries whose score changed and the IDs not found (nothing is set for those). To order a single collection by hand, use set_collection_positions instead.

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": {
      "scores": "<scores>"
    },
    "name": "set_entry_scores"
  }
}

Input Schema

NameRequiredDescriptionDefault
scoresYesThe entries to score

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the supplied annotations it discloses that scores are user-scoped and apply in every list the entry belongs to, that previous scores are overwritten, and that partial failures are possible (not-found IDs get nothing set). It also describes the return payload (changed entries plus not-found IDs), which the annotations do not cover.

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 dense sentences, front-loaded with the action and scope, then sorting semantics, then the sibling alternative. No filler; each clause carries either behavior, routing, or return information.

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?

For a single-parameter mutation tool with no output schema, the description covers mutation semantics, cross-list scope, overwrite behavior, partial-failure handling, and the return shape. 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%, so the baseline is 3, but the description adds real meaning the schema lacks: a score is user-level and therefore visible across all lists, and null clears rather than zeroes. The 1000-entry cap is repeated from schema maxItems, which adds nothing.

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?

The description names a specific verb and resource ('Set or clear (null) numeric scores on up to 1000 entries') and states its purpose (prioritizing the user's reading). It explicitly distinguishes itself from the closest sibling, set_collection_positions, so an agent can route without opening either schema.

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?

It states the downstream effect that motivates use (lists sorted by score show higher scores first, then unscored) and names the alternative plus the condition that selects it: 'To order a single collection by hand, use set_collection_positions instead.' Both when-to-use and when-to-use-something-else are covered.

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