Skip to main content
Glama

Get today's reading connections

get_daily_reading_connections
Idempotent

Returns today's connections in the reader's reading: passages from different books they are reading, and from their saved quotes and notes, that share a theme, with the theme named and a question to reflect on. The text of a passage from a book is returned only when the reader uploaded their own copy of that book in the ReadingRate app, and a poem's text only when get_poem may show that poem; otherwise the connection gives the book or poem and the page without the text. The first call each day creates them: ReadingRate sends a few of those passages to its AI provider to name the theme and write the question, then stores the result in the reader's account and counts it against their ReadingRate AI usage. Later calls the same day return the same connections.

Use when the reader asks what connects their recent reading, or for today's reading connections or reflection prompt.

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": "get_daily_reading_connections"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
themeNoThe theme connecting today's passages
messageNoWhy there is nothing today, when there is not
connectionsNoThe connected passages
generated_atNoWhen today's connections were made
reflection_promptNoA question for the reader to reflect on

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / connections / items / properties / content / description
      Added value: +"The passage. Absent when its text is withheld: a book the reader has not uploaded their own copy of, or a poem ReadingRate may not show"
    • addedOutput schema / properties / connections / items / properties / text_available
      Added value: +{
      +  "description": "False when the passage's text is withheld; the book and page are still given",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

This is the standout section: it discloses that the first call each day creates the connections, sends a few passages to an AI provider, stores the result in the reader's account, and counts against their AI usage, while later calls the same day return the same result. That explains why readOnlyHint is false despite the 'Get' name and why idempotentHint is true, and it surfaces a quota cost the agent must know about. It also explains the text-availability rule tied to the reader's own uploaded copies and poem visibility.

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?

It is front-loaded with what is returned, then the creation/quota mechanics, then usage guidance — a sensible order. The second sentence is long and packs text-availability exceptions into one run-on clause, which costs some readability, but every sentence carries information an agent needs.

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?

Given zero inputs, an existing output schema (so return shape need not be restated), and non-obvious side effects (AI provider call, stored result, usage accounting), the description covers everything an agent needs: what it returns, when to call it, what the first call costs, and when text is omitted. Nothing material is left unexplained.

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?

The tool takes zero parameters, so there is no parameter meaning to add; the baseline for a no-parameter tool applies. The description does not mislead about inputs and correctly implies the tool is scoped to 'today' with no arguments.

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 gives a precise verb and resource — it returns today's connections: passages from different books, saved quotes, and notes that share a theme, plus the named theme and a reflection question. It also distinguishes itself from related tools by explaining when poem text appears (only when get_poem may show that poem), so an agent can tell what this tool yields versus siblings like find_related_passages.

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 states explicitly: 'Use when the reader asks what connects their recent reading, or for today's reading connections or reflection prompt.' That is a clear triggering condition. It does not name an alternative tool to use instead when the reader wants something else (e.g., related passages search), so it stops short of full when/when-not routing.

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.