Skip to main content
Glama

Niche of One Network

My highlights and notes

reader_notes
Read-onlyIdempotent

Members. List or search your OneReader highlights, notes and bookmarks, for one book or all books. Each has an id for editing.

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_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoOne note by id.
bookNoBook title or id, as reader_library lists it.
kindNo
queryNoWords to find in quotes and notes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: results carry ids usable for editing, and retrieval can span one or all books. It omits pagination, result caps, ordering, and what 'Members' actually constrains (auth/plan requirement), which is the one piece of context that could change an agent's behavior.

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?

Two compact sentences carry the core purpose, scope, and the downstream id relationship with no padding. The leading 'Members.' fragment is cryptic and front-loads ambiguity rather than the key action, which keeps it out of 5 territory.

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

Completeness3/5

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

For a read-only, zero-required-param listing tool with annotations present and no output schema, this is roughly adequate — mention of returned ids partly compensates for the missing output schema. Still missing are result volume/pagination expectations and any note that combining parameters filters rather than errors, which matters for a 4-param search tool.

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 75%, so the baseline is 3. The description reinforces meaning for `book` (one book or all books) and implies the `id` in results is the editing handle, but says nothing about `kind` filtering or how `query` matching works ('quotes and notes' is only in the schema). Marginal value over the schema.

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?

Specific verb pair (list or search) plus concrete resource (OneReader highlights, notes and bookmarks) and scope (one book or all books). An agent can immediately tell this is a read/retrieval tool for notes. It stops short of 5 because it never contrasts itself with plausible siblings like reader_export_notes or outline_from_notes, so the boundary is only inferable from the verb.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'for one book or all books' implies the two usage modes, and 'Each has an id for editing' hints that results feed the note-editing/naming flow. However, there is no explicit when-to-use vs when-not, and no pointer to alternatives for exporting or summarizing notes. Guidance is implied rather than stated.

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