Skip to main content
Glama
Sign In

MemoryBrain

by ai.memorybrain
OverviewDiscussionsAdmin

Tus chats importados

list_chats
Read-only

Lista los chats que el usuario ha importado, los más recientes primero: título, fecha, mensajes, cuántas palabras escribió él (mine) y si ya se han extraído. Úsala para elegir de cuáles sacar notas o cuando pregunte qué chats tiene; query filtra solo por el título, no por el contenido. Léelos con read_chat.

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

Input Schema

NameRequiredDescriptionDefault
limitNoCuántos devolver (40 por defecto).
queryNoFiltra por palabras del título.
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.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that: result ordering, which fields come back, that 'mine' counts words written by the user, and whether extraction has occurred. It does not discuss pagination behavior or limits, 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?

Three compact sentences with the resource and ordering front-loaded, followed by usage and the sibling pointer. The first sentence packs a long field list and is somewhat run-on, but nothing is redundant.

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

Completeness5/5

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

With four optional params, no output schema and read-only annotations, the description supplies everything an agent needs: what is listed, in what order, what fields come back, how the filter behaves, and which tool to call next. No meaningful gap remains.

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, and the description earns above baseline by clarifying that query filters only on title and not on content, which the schema's "Filtra por palabras del título" only implies. Limit, offset and pending are left entirely to the schema, which is acceptable given full coverage.

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+resource ("Lista los chats que el usuario ha importado") plus ordering ("los más recientes primero") and the fields returned (título, fecha, mensajes, mine, extraído). It also names the sibling read_chat, so an agent can distinguish it from listing vs. reading 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 explicit when-to-use conditions: to pick which chats to take notes from, or when the user asks what chats they have. It also routes to the alternative ("Léelos con read_chat") and warns about the query limitation, leaving little to inference.

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