Skip to main content
Glama
Sign In

MemoryBrain

by ai.memorybrain
OverviewDiscussionsAdmin

Guardar dónde lo dejas

save_context
Idempotent

Guarda en qué está el usuario y qué queda pendiente, para que otra conversación (en otro cliente o en el móvil) lo retome. Sustituye lo anterior: manda el estado entero, corto.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "focus": "<focus>"
    },
    "name": "save_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
focusYesEn qué está, en una o dos frases.
pendingNoLo que queda pendiente, una línea por cosa (máximo 10). Va como tareas al proyecto «Recados»: si es de un proyecto concreto, mejor apúntalo ahí con update_project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / pending / description
      Previous value: -"Lo que queda pendiente, una línea por cosa (máximo 10)."New value: +"Lo que queda pendiente, una línea por cosa (máximo 10). Va como tareas al proyecto «Recados»: si es de un proyecto concreto, mejor apúntalo ahí con update_project."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare a non-read-only, idempotent, non-destructive local write. The description adds genuinely new behavioral context by disclosing overwrite semantics ('Sustituye lo anterior'), which is consistent with idempotentHint=true and not contradictory with destructiveHint=false since a snapshot replace is reversible in spirit and re-sendable. It also sets an expectation of brevity ('corto'), though it says nothing about size limits or error behavior beyond the schema.

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?

Two short sentences, front-loaded with the purpose and then the replacement constraint. Nothing redundant; every clause carries information the agent needs before calling.

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?

For a two-parameter write tool with fully documented schema, no output schema, and annotations covering the safety profile, the description supplies everything needed: what it stores, why, and that it replaces rather than appends. No material gap remains.

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 the baseline is 3: the schema already explains focus and pending thoroughly, including the Recados project routing and the max-10 limit. The description only adds a generic brevity hint ('corto') and no format or syntax detail beyond 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?

States a concrete verb and object: it saves what the user is working on and what is pending so another conversation (different client or mobile) can resume it. That is clearly distinct from retrieval siblings like get_context and from note-saving siblings like save_output or save_highlights, though the description never names the counterpart tool explicitly.

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?

The context for use is clear: call it when state must survive into another session/device. It also gives a usage rule ('manda el estado entero'), but offers no explicit when-not-to-use or alternative routing (e.g., the schema mentions update_project for project-specific items, but the description itself does not).

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