Skip to main content
Glama
Sign In

Lion Reader

by com.lionreader
OverviewDiscussionsAdmin

count_entries

Read-only

Get the unread count of one list as { unread, asOf }: all entries by default, or pass at most one of subscriptionId, tagId, uncategorized, type and starredOnly (more is an invalid-arguments error). An ID that isn't one of the user's subscriptions or tags counts 0. Cheaper than paging through list_entries when you only need the number; list_tags and list_subscriptions include unread counts per tag and subscription.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "count_entries"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoCount unread saved articles
tagIdNoCount a tag's unread entries
starredOnlyNoCount unread starred entries
uncategorizedNoCount unread entries in untagged subscriptions
subscriptionIdNoCount a subscription's unread entries (a feed, a collection or Saved)

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?

Annotations only declare readOnlyHint and openWorldHint; the description adds substantive behavior the agent could not get elsewhere: the exact response shape, that supplying more than one filter is an invalid-arguments error, and that an unknown subscription/tag ID returns 0 rather than failing. That covers success, error, and edge-case semantics.

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?

Two dense sentences, front-loaded with the verb and return shape, then the filter constraint, then the routing guidance. No filler and no repetition of the schema's per-parameter text.

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?

There is no output schema, and the description compensates by spelling out the returned object. For a read-only counting tool with five optional parameters, everything needed to call it correctly and interpret the result is present.

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 per-parameter definitions are already documented and the baseline would be 3. The description still adds meaning the schema cannot express: the at-most-one cross-parameter constraint and the zero-count behavior for IDs outside the user's subscriptions or tags.

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 — 'Get the unread count of one list' — and even gives the return shape '{ unread, asOf }'. It names the sibling tools it supersedes (list_entries, list_tags, list_subscriptions), so the agent can place it precisely in the toolset.

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 says when this is the right call ('Cheaper than paging through list_entries when you only need the number') and when a sibling is preferable ('list_tags and list_subscriptions include unread counts per tag and subscription'). It also states the mutual-exclusion rule up front, so there is little left to infer.

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