Skip to main content
Glama
Sign In

MemoryBrain

by ai.memorybrain
OverviewDiscussionsAdmin

Leer una nota

read_note
Read-only

Devuelve una nota entera del cerebro del usuario, con su fuente, sus enlaces tipados (links) y las notas que la enlazan (backlinks). Úsala tras search_brain con las notas que vas a citar; para orientarte basta search_brain. Queda apuntada como leída.

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": {
      "id": "<id>"
    },
    "name": "read_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesEl id que dio search_brain (en un cerebro conectado, su id o ruta; vale con prefijo, «carlos:…»).
brainNoEn qué cerebro, si no es el del usuario (list_brains).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Beyond readOnlyHint/openWorldHint, the description discloses the return payload (source, typed links, backlinks) and a non-obvious side effect: "Queda apuntada como leída." That side-effect disclosure is the kind of context annotations cannot express. It stops short of covering permissions or behavior when the id is ambiguous or not found.

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 short sentences, front-loaded with what is returned, then the routing rule, then the side effect. Every clause carries information; 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?

There is no output schema, so the description must say what comes back, which it does precisely (full note plus source, links, backlinks). Combined with the read-tracking side effect and the search_brain routing rule, an agent has everything needed to call it correctly.

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%: the id parameter already documents that it comes from search_brain, accepts a path or prefixed form ("carlos:…"), and brain is documented via list_brains. The description adds no parameter-level meaning beyond that, 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?

"Devuelve una nota entera del cerebro del usuario" names a specific verb and resource, and the sentence goes on to enumerate what comes back (fuente, enlaces tipados, backlinks). It is immediately distinguishable from search_brain, which the description explicitly frames as the orientation tool.

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?

Explicit sequencing guidance: "Úsala tras search_brain con las notas que vas a citar; para orientarte basta search_brain." This tells the agent both when to call it (after search, for notes to cite) and when not to (mere orientation), naming the alternative.

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