Skip to main content
Glama
Sign In

ReadingRate

by com.readingrate
OverviewDiscussionsAdmin

Save a quote link

save_quote_link
Idempotent

Links two of the reader's saved quotes in ReadingRate, with an optional line on why they belong together. The link is two-way and shows on both quotes in the app. Linking two quotes that are already linked changes nothing.

Use only when the reader asks to link two quotes, or says yes to linking them. To propose a link the reader has not asked for, use suggest_quote_link.

Example: {"quote_id": "", "linked_quote_id": "", "note": "Both ask how wide the present is."}

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>"
    },
    "name": "save_quote_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoOptional: 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; nothing changed

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Goes beyond annotations by explaining the concrete effects: the link is two-way, appears on both quotes, and re-linking already-linked quotes is a no-op (making the idempotentHint tangible rather than abstract). It does not address permissions or what a partial/failed link leaves behind, so it falls short of a 5 with annotations already carrying the safety profile.

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?

Front-loads the action and effect, then the usage rule, then a concrete example. No sentence is filler; even the idempotency sentence preempts a real agent question.

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 3-parameter, non-destructive, idempotent write tool with an output schema and full schema coverage, the description supplies everything else an agent needs: trigger condition, alternative for the unsolicited case, side effect, and a call example.

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?

Schema coverage is 100%, so both ids and the 280-character note limit are already documented. The description adds a worked example showing all three fields populated and clarifies the intent of note ('why they belong together'), which is mild added value over a schema that already does the heavy lifting.

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?

Specific verb (links) plus specific resource (two of the reader's saved quotes) with an optional rationale note. It is immediately distinguishable from the sibling suggest_quote_link, which is named later in the same description.

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?

States an explicit positive trigger (the reader asks to link, or says yes to linking) and an explicit negative case with the correct alternative: 'To propose a link the reader has not asked for, use suggest_quote_link.' That is exactly the when/when-not/alternative triad.

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