Skip to main content
Glama

Niche of One Network

Notes for an outline

outline_from_notes
Read-onlyIdempotent

Members. Gather your OneReader highlights and notes on a topic or book so you can outline a post from them. Returns the notes; the outline is yours to write.

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

Input Schema

NameRequiredDescriptionDefault
bookNoBook title or id, as reader_library lists it.
topicNoWords to find in your 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 readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact — it returns notes, not an outline — but says nothing about result volume, what happens when both optional filters are omitted, or how book and topic combine.

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 the key clarification (returns notes, not an outline) given last for emphasis. The fragment 'Members.' is unexplained and mildly wasteful, but overall there is little filler.

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 two-parameter, zero-required read tool with no output schema, the description covers what it does and roughly what comes back. It stops short of explaining behavior with no filters supplied, which is a real gap given that nothing is required, and it leaves the 'Members.' membership implication unexpanded.

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%, with both parameters fully described in-schema (book 'as reader_library lists it,' topic 'words to find in your notes'). The description's phrase 'on a topic or book' slightly reinforces that the filters are alternative or combinable, but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 ('gather your OneReader highlights and notes') scoped to 'a topic or book', and it corrects the misleading name by clarifying that no outline is generated. It does not explicitly distinguish itself from reader_notes or reader_export_notes, but the purpose itself is unambiguous.

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 by the stated scenario ('so you can outline a post from them'), which tells the agent the intent but not the boundaries. There is no indication of when to prefer this over its sibling note-retrieval tools, nor any exclusion or prerequisite beyond the cryptic 'Members.' opener.

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