Skip to main content
Glama
Sign In

MemoryBrain

by ai.memorybrain
OverviewDiscussionsAdmin

Desconectar un cerebro

disconnect_brain
Idempotent

Quita un cerebro conectado al del usuario, solo cuando él lo pida: deja de poder buscar y leer en él. Es lo contrario de connect_brain; para quitar a otros el acceso al suyo, usa unshare_brain. Lo que guardó de él con keep_note se queda en su cerebro.

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

Input Schema

NameRequiredDescriptionDefault
idYesEl cerebro conectado, tal como sale en list_brains.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / id / description
      Added value: +"El cerebro conectado, tal como sale en list_brains."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Goes beyond the annotations by describing the effect: the user can no longer search or read in that brain, and notes saved via keep_note survive on the user's side. This clarifies the destructiveHint=false profile by explaining exactly what is and is not lost, though it does not state that reconnecting is the way to restore access.

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?

Front-loads the action, then the permission constraint, then the sibling routing and the side effect. Every clause earns its place; only the retention clause could be trimmed for a shorter read.

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?

A one-parameter tool with full schema coverage, no output schema, and idempotency already declared in annotations. The description supplies the scoping rule and side-effect information an agent needs; only the reconnect path is left implicit.

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% and the single id parameter is already documented as coming from list_brains, so the description adds no meaning beyond the schema. Baseline 3 applies when the schema carries parameter semantics.

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 in the first clause ("Quita un cerebro conectado al del usuario") and immediately contrasts it with connect_brain and unshare_brain, so the agent can tell the three apart without opening any 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 an explicit precondition ("solo cuando él lo pida"), names the inverse operation, and routes to the correct sibling for the different case of revoking someone else's access (unshare_brain). Both when-to-use and when-not-to-use are covered.

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