Skip to main content
Glama

capture

Idempotent

Save a standalone idea that persists across tasks. Use when you reach a stable synthesis or discover a reusable pattern; includes deduplication and returns related suggestions.

Instructions

Capture a new durable idea. Use when: you reach a stable synthesis; you discover a reusable pattern; you want a standalone idea that should survive task boundaries; a checkpoint has hardened into a first-class concept. If you only need a lightweight in-progress trace, use checkpoint instead. content is required. scope and actor default from cwd and environment. Optional task_ref groups all writes from the same task; it is normalized to lowercase kebab-case at the boundary, so 'Writeback Phase 1', 'writeback_phase_1', and 'writeback-phase-1' collapse onto the same key. Returns annotate_candidates and related_candidates so the next memory move is obvious. candidates (default 5, max 10, 0 to skip) controls how many annotate/related suggestions are returned — set to 0 for a fire-and-forget trace where you don't intend to act on suggestions, or raise to 10 when actively triaging. Deduplication: same actor + same content within 5 seconds is silently treated as the same write. Beyond the 5-second window, or across actors, content with the same SHA-256 hash (whitespace-collapsed, lowercased) in the same scope dedupes against the original idea — incoming tags are merged in and a dup_attempt note is appended for provenance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYes
scopeNo
tagsNo
originatorNo
task_refNo
candidatesNo
actorNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Annotations confirm mutating (readOnlyHint=false) and idempotent (idempotentHint=true). Description adds rich behavioral details: 5-second dedup window, SHA-256 dedup beyond window, tag merging, and 'dup_attempt' note. 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?

Description is long but well-structured with 'Use when:' and clear breakdowns. Each sentence provides essential information. Slightly verbose due to detailed dedup rules, but efficiency is high given complexity.

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?

Covers purpose, usage, parameter behaviors, deduplication, and return value. Explains edge cases (fire-and-forget, raising candidates) and provenance. Almost no gaps remain for the agent.

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 0%, but description compensates: states 'content is required', explains defaults for scope/actor, normalizes task_ref to kebab-case, and documents candidates (default 5, max 10, 0 to skip). Missing detail on tags and originator, but still adds significant value.

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 'Capture a new durable idea' and distinguishes the tool from sibling 'checkpoint' by specifying when to use each. It also mentions the return value (candidates), making the purpose unambiguous.

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?

Explicitly lists conditions for use ('stable synthesis', 'reusable pattern', 'standalone idea') and contrasts with 'checkpoint'. Provides guidance on 'candidates' parameter (set to 0 for fire-and-forget, raise to 10 for triaging) and explains deduplication behavior.

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/CobraChickenAI/ideahub_mcp'

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