Skip to main content
Glama
Sign In

MemoryBrain

by ai.memorybrain
OverviewDiscussionsAdmin

Tus libros de Kindle importados

list_books
Read-only

Lista los libros con subrayados importados: título, autor, cuántos subrayados y notas suyas, si ya se han extraído (saved = notas guardadas) y la última tanda guardada (parts: la siguiente es parts + 1). Úsala para elegir de qué libro sacar notas o cuando pregunte qué subrayados tiene; léelos con read_book.

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

Input Schema

NameRequiredDescriptionDefault
limitNoCuántos devolver (40 por defecto).
queryNoFiltra por título o autor.
offsetNoCuántos saltar, para paginar (0 por defecto).
pendingNoSolo los que aún no se han extraído.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Cuántos devolver (40 por defecto)."
    • addedInput schema / properties / offset / description
      Added value: +"Cuántos saltar, para paginar (0 por defecto)."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description adds the important non-structured detail: what each returned field means, notably 'saved = notas guardadas' and how to advance batches with 'parts: la siguiente es parts + 1'. It stops short of stating pagination defaults or whether the highlight/note counts are truncated, 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One dense sentence listing returned fields plus a short instruction sentence; the purpose is front-loaded and nothing is wasted. The field list is somewhat run-on, but every clause carries information about the response.

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?

With no output schema, the description correctly compensates by explaining the shape of each result row, including the tricky saved/parts semantics needed to continue reading a book's highlights. Remaining gap is how batching relates to limit/offset pagination, which an agent would have to infer.

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 description coverage is 100%, so limit, query, offset and pending are already documented in the schema. The description adds no extra syntax, filtering behavior or interaction between limit/offset and the parts batching, so the baseline 3 applies.

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 ('Lista los libros con subrayados importados') and enumerates the fields returned (título, autor, número de subrayados y notas, saved, parts). It also names the sibling used for the next step ('léelos con read_book'), so an agent can distinguish it from read_book or search_brain without opening a schema.

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

Usage Guidelines5/5

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

Gives two concrete selection contexts ('para elegir de qué libro sacar notas', 'cuando pregunte qué subrayados tiene') and routes the follow-up read to read_book explicitly. That is an when-to-use plus an alternative, not just implied usage.

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

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