Skip to main content
Glama
Sign In

ReadingRate

by com.readingrate
OverviewDiscussionsAdmin

Suggest a quote link

suggest_quote_link
Idempotent

Suggests a link between two of the reader's saved quotes in ReadingRate, with a line on why they belong together. The suggestion waits in the app until the reader accepts or dismisses it; it is not a link until they accept.

Use when you notice two of the reader's quotes, usually from different books, that speak to each other in a way the reader may not have seen, and the reader has not asked you to link them. Say in the conversation which two you suggested and why. Check list_quote_links first so you do not suggest a link they already have.

Example: {"quote_id": "", "linked_quote_id": "", "note": "Both describe living only in the present."}

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": {
      "quote_id": "<quote_id>",
      "linked_quote_id": "<linked_quote_id>",
      "note": "<note>"
    },
    "name": "suggest_quote_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteYesOptional: one line on why the two belong together, at most 280 characters
quote_idYesOne of the two quotes: its id, from list_saved_quotes
linked_quote_idYesThe other quote: its id, from list_saved_quotes

Output Schema

NameRequiredDescriptionDefault
linkNo
messageNo
already_linkedNoTrue when the two were already linked or suggested; nothing changed

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

The description adds substantial behavioral context beyond the annotations: the result is only a pending suggestion, not an actual link until accepted or dismissed. It also discloses the deduplication check and the conversational expectation, which are important for using this mutation tool correctly.

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?

The description is front-loaded with the key pending-suggestion behavior, then covers usage, deduplication, and an example. Despite being several sentences long, each part contributes useful operational context without unnecessary repetition.

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 the presence of an output schema, the description does not need to explain return values. It covers the key lifecycle behavior, usage conditions, duplicate avoidance, and required conversational transparency, leaving no major gap for an agent to call this tool correctly.

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?

With 100% schema description coverage, the schema already explains all three parameters. The description reinforces the meaning of note as a one-line rationale and provides an example, but it does not add much parameter detail beyond the structured 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?

The description states a specific verb and resource: it suggests a link between two saved quotes, with a note explaining why they belong together. It also distinguishes the action from creating a real link by explaining that the suggestion remains pending until the reader accepts it.

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 gives clear when-to-use guidance: when the reader has not asked for a link but two saved quotes speak to each other, usually across books. It also names a concrete prerequisite, checking list_quote_links first to avoid duplicate suggestions, and tells the agent what to say in conversation.

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

All ReadingRate 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