Skip to main content
Glama

Niche of One Network

Export my notes as Markdown

reader_export_notes
Read-onlyIdempotent

Members. Your OneReader highlights, notes and bookmarks as Markdown, for one book or all. Long text: best shown to the user as a document or artifact.

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

Input Schema

NameRequiredDescriptionDefault
bookNoBook title or id, as reader_library lists it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this as a safe, idempotent, non-destructive read. The description adds useful behavior beyond that: output is Markdown, can cover one book or all, and long results should be surfaced as a document or artifact. It still does not describe return shape, pagination, or size limits.

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?

Three short sentences with no wasted wording; the core action and scope are front-loaded. The opening 'Members.' is a little abrupt, but the rest is compact and actionable.

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 simple one-optional-parameter read tool with rich annotations and no output schema, the description covers what is exported, the output format, optional scoping, and how to present long results. Minor gaps around exact return structure are acceptable given the simplicity and absence of an output schema.

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?

Schema coverage is 100%, so the schema already documents the single optional book parameter. The description adds meaning by clarifying that omitting the book yields notes for all books, which is useful default behavior not stated in 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?

The description states a specific verb and resource ('export ... highlights, notes and bookmarks as Markdown') and clarifies the scope ('for one book or all'). It is clear enough to distinguish from a simple notes-reading tool, though it does not explicitly name or contrast with reader_notes.

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?

Usage is implied: export all notes or restrict to one book, and present long output as a document or artifact. However, it gives no explicit when-to-use guidance versus alternatives such as reader_notes or outline_from_notes, and no exclusions or prerequisites beyond the terse 'Members.'

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