Skip to main content
Glama

Niche of One Network

Save a highlight or note

reader_note_save

Members. Add a highlight, note or bookmark to a book in your OneReader library, or edit one of yours by id. Shows a preview first; call again with confirm true to save.

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

Input Schema

NameRequiredDescriptionDefault
idNoEdit this note (from reader_notes).
bookNoBook title or id, as reader_library lists it.
kindNo
noteNoYour note.
colorNoHighlight color name.
quoteNoThe passage.
confirmNoLeave out to preview. true writes it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly false, destructive false, idempotent false), so the bar is lower; the description nonetheless adds behavior not in the annotations — that the first call is a non-committing preview and the write only occurs on a repeat call with confirm true. It omits what the preview returns and whether an edit overwrites unmentioned fields, which keeps it from a 5.

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 tight sentences with no filler: audience scope first, capability second, the preview/confirm workflow last. Every clause carries information the agent needs to invoke it correctly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter, zero-required, mutating tool with no output schema, the description covers the essential workflow and ownership scoping ('one of yours'). It leaves minor gaps — what the preview shows, and how create vs. edit argument combinations are validated — but nothing that would likely cause a wrong first call.

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 86%, so the schema already documents id, book, note, color, quote and confirm in detail. The description reinforces the id-as-edit and confirm-as-write semantics but adds no new constraints (e.g. whether id and book are mutually exclusive, or which fields apply per kind), which matches the baseline of 3 when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 ('Add a highlight, note or bookmark to a book in your OneReader library') and covers the secondary edit mode ('edit one of yours by id'), so an agent can tell this apart from a pure writer/draft tool by the OneReader library scope. It stops short of explicitly differentiating from siblings such as save_to_onewriter or send_highlight_to_draft, leaving that inference to the resource wording.

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 gives clear operational guidance: use 'id' to edit an existing item, and the mandatory two-step pattern — call without 'confirm' for a preview, then call again with confirm true to actually write. It does not state when to prefer this over adjacent tools (e.g. save_to_onewriter) or what to do if a note already exists, so no explicit exclusions are provided.

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.

Resources