Skip to main content
Glama

Capture context

mindmap_capture

Capture a portable summary of the current session so you can resume the discussion later in any AI tool.

Instructions

Silently save a portable context summary from the current session so it can be resumed later in any tool. This is the effortless 'capture' half of the loop. New captures start as 'captured' (warm tier); they become trusted 'promoted' memories the first time you resume them.

CALL THIS PROACTIVELY (you don't need to be asked) when: a substantive discussion is wrapping up; the user says they're done / switching tasks / "remember this" / "save this"; a key decision, plan, or conclusion was reached; or the user signals they'll continue later. Write the summary so a future session in a DIFFERENT tool could pick up with full context. Skip trivial one-off exchanges.

Args:

  • title (string): short topic title

  • summary (string): the portable context to inject into a future session (markdown ok)

  • key_points (string[]): scannable discussion points (optional)

  • tags (string[]): topic tags for filtering (optional)

  • source (string): Origin tool, e.g. 'claude-code', 'chatgpt', 'chat', 'cowork', 'claude-desktop'.

  • links (string[]): ids of related threads to connect (optional)

  • kind ('discussion'|'brainstorm'): mark brainstorm sessions so they can be resumed/clustered as ideas (default 'discussion')

Returns: the created thread id and its formatted record.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesShort topic title
summaryYesPortable context summary (markdown ok)
key_pointsNoScannable discussion points
tagsNoTopic tags for filtering
sourceNoOrigin tool, e.g. 'claude-code', 'chatgpt', 'chat', 'cowork', 'claude-desktop'.unknown
linksNoids of related threads to link
kindNoThread kinddiscussion
Behavior4/5

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

Annotations are minimal (non-readonly, non-destructive, non-idempotent). Description adds behavioral traits: silent save, tier lifecycle (captured -> promoted), portability across tools. No contradictions.

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?

Well-structured with purpose first, then usage guidance, then parameters. Slightly verbose but all sentences add value. Could trim repetitive schema descriptions.

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?

Given 7 params and no output schema, the description covers purpose, usage, parameter meanings, and return value. Sufficient for an agent to decide and invoke correctly.

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%, but description's 'Args' section adds context like source meaning origin tool and kind meaning brainstorm vs. discussion. Provides value beyond schema alone.

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 clearly states it silently saves a portable context summary for later resumption. It distinguishes from siblings like mindmap_resume by being the 'capture half of the loop'.

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 guidance on proactive calling: substantive discussion wrap-up, user signals, key decisions. Also specifies when not to use (trivial exchanges). Differentiates from other tools via the capture/resume loop.

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/ravi-labs/mindmap-mcp-server'

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