Skip to main content
Glama
Sign In

ThinkerNotes

by com.thinkernotes
OverviewDiscussionsAdmin

Search literature notes

search_literature_notes
Read-onlyIdempotent

Search the user's literature notes (notes taken on books, articles and podcasts) by keyword in the note text, not the title or author of the book. Matches the words in the text, not the meaning, so try another wording if nothing is found. To get the notes on one specific book, article or podcast, pass its id as collection_id.

Input Schema

NameRequiredDescriptionDefault
queryNoOptional keyword to narrow the notes by their text. With collection_id, leave it out to list every note in that collection
collection_idNoOnly return the notes in this collection (its id)

Output Schema

NameRequiredDescriptionDefault
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / collection_id
      Added value: +{
+  "description": "Only return the notes in this collection (its id)",
+  "type": "integer"
+}
    • removedInput schema / properties / media_id
      Removed value: -{
-  "description": "Only return the notes on this media item (its id)",
-  "type": "integer"
-}
    • changedInput schema / properties / query / description
      Previous value: -"Optional keyword to narrow the notes by their text. With media_id, leave it out to list every note on that item"New value: +"Optional keyword to narrow the notes by their text. With collection_id, leave it out to list every note in that collection"
    • addedOutput schema / properties / items / items / properties / collection_id
      Added value: +{
+  "description": "Id of the collection (the book, article or podcast) the note was taken on",
+  "type": "integer"
+}
    • removedOutput schema / properties / items / items / properties / media_id
      Removed value: -{
-  "description": "Id of the book, article or podcast the note was taken on",
-  "type": "integer"
-}
    • changedOutput schema / properties / items / items / required
      Previous value: -[
-  "id",
-  "excerpt",
-  "media_id",
-  "created_at"
-]New value: +[
+  "id",
+  "excerpt",
+  "collection_id",
+  "created_at"
+]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive behavior, so the key added value is the matching semantics: literal word matching rather than meaning-based search, restricted to note text. That is genuinely useful behavioral context an agent would otherwise have to discover empirically. Pagination and result-size behavior are not covered, but an output schema exists.

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 sentences, each front-loaded with the constraint that matters most: what is searched, how matching works, and the alternate retrieval path. No repetition of the schema and no filler.

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 two-optional-parameter read tool with an output schema and full annotation coverage, the description supplies what is needed to call it correctly. The one gap is what happens when both parameters are omitted, which the description never addresses.

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 baseline is 3; the description goes further by explaining that collection_id corresponds to 'one specific book, article or podcast', clarifying that a collection is the source work rather than an arbitrary grouping. The 'leave it out to list every note' behavior is documented only in the schema, not the description.

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?

States a specific verb and resource ('Search the user's literature notes') and immediately scopes the search domain: keyword matching in note text, explicitly 'not the title or author of the book'. It also names a distinct access pattern (fetch by collection_id), so an agent can tell it apart from list_recent_literature_notes or get_literature_note.

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?

Gives clear when-to-use guidance: keyword search over note text, with the explicit fallback 'try another wording if nothing is found' and a route to single-work retrieval via collection_id. It does not name or exclude any sibling tool by name, so the agent must infer the boundary against list_recent_literature_notes and get_literature_note.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ThinkerNotes 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