Skip to main content
Glama

Remember / Save Context

bridge_save_context

Save key decisions, preferences, and insights across all Claude surfaces for persistent recall in future conversations.

Instructions

Remember something for later. Use this when the user says things like "remember this", "save this", "note this", "keep this for later", "don't forget", or when an important decision, preference, or insight comes up that should persist across conversations. This saves context that will be available in ALL Claude surfaces (Chat, Code, Cowork) — even in future sessions. Use proactively when you recognize something worth remembering: a decision made, a user preference expressed, a lesson learned, a key file identified, or a workflow established.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoShort labels for categorization. Examples: ['frontend', 'react'], ['deploy', 'ci-cd'], ['auth']. Helps with filtering later.
typeYesClassify the context: "decision" when the user chose between options (e.g. "let's use PostgreSQL", "we'll go with REST not GraphQL"). "preference" when the user expresses how they like things done (e.g. "I prefer tabs", "use French for conversation", "keep responses short"). "insight" when a fact or lesson is discovered (e.g. "the API rate-limits at 100 req/s", "that bug was caused by timezone handling"). "file_ref" when a key file is identified (e.g. "src/auth.ts handles all JWT logic"). "workflow" for processes (e.g. "deploy flow: merge → CI → staging → prod"). "note" for anything else worth remembering.
contentYesWhat to remember. Write it clearly so it will be useful when retrieved later by any Claude surface.
projectNoProject name if this context is project-specific. Use the same name consistently (e.g. "acme-site", "payments-api"). Omit for personal preferences or general notes.
source_surfaceYesWhere this conversation is happening. "chat" for Claude.ai chat, "code" for Claude Code (terminal/IDE), "cowork" for Claude Cowork sessions.
response_formatNoResponse format: json or markdownmarkdown
Behavior4/5

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

Annotations indicate readOnlyHint=false and destructiveHint=false, consistent with a write operation. Description adds that saved context persists across all surfaces and sessions, which is key behavioral context beyond the annotations.

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-loaded with purpose, then usage triggers and examples. Every sentence adds value, though slightly verbose; could be streamlined slightly.

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 6 parameters and no output schema, the description adequately explains usage, types of content, and cross-surface persistence. Lacks return value details but output schema is absent.

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 covers 100% of parameters with descriptions. The description enriches the 'type' enum with detailed examples and context, adding value beyond the schema.

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?

The description states 'Remember something for later' with specific triggers and examples of what to save, clearly distinguishing from siblings like bridge_delete_context or bridge_get_context which handle retrieval/deletion.

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?

Provides explicit when-to-use guidance (user phrases like 'remember this', proactive saving) and what types of info to save, but doesn't explicitly exclude scenarios or mention alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/timmx7/acheron-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server