Skip to main content
Glama

write_task_memory

Save reusable task insights—pitfalls, fixes, decisions, patterns—as durable ChatCrystal notes. Validates quality and skips weak writebacks.

Instructions

Persist a task memory only when it can become a high-quality ChatCrystal note: specific title, concrete summary, meaningful key conclusions, and a durable reusable lesson such as a pitfall, fix, decision, pattern, or symptom-to-resolution mapping. Do not write one-time environment checks, version/status reports, ordinary progress logs, or vague robustness claims. Weak auto writebacks are skipped by core validation and recorded only as receipts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYesUse auto for agent-generated writebacks and manual for explicit user-curated memories.
source_run_keyNoIdempotency key for auto writebacks; required in auto mode to avoid duplicate memory receipts.
scopeNoStore as project memory by default; global is reserved for broadly reusable manual lessons.
taskYesCurrent task context used to scope, rank, and store memories.
memoryYesCandidate ChatCrystal note content to validate or persist as reusable task memory.
Behavior3/5

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

Discloses quality validation and skip behavior for weak entries, but with no annotations, it misses details like side effects, auth requirements, rate limits, or error handling. The description carries the full burden due to missing 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?

Description is a single paragraph that is front-loaded with purpose and criteria. It includes examples and exclusions without excessive verbosity. Could be slightly more concise but effectively conveys key information.

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 the complex nested parameters and no output schema, the description covers purpose, usage conditions, and quality expectations. It lacks explanation of return values (receipts) but otherwise is fairly complete.

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 description coverage is 100%, so parameters are well-documented in the schema. The description adds context on quality criteria but does not enhance parameter meaning beyond what the schema provides. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool persists high-quality task memories as ChatCrystal notes with specific criteria (title, summary, conclusions, reusable lesson). It distinguishes from weak auto writebacks but does not explicitly differentiate from sibling tools like validate_task_memory or recall_for_task.

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 (only for high-quality, durable lessons) and when-not-to-use (one-time checks, status reports, vague claims). Mentions that weak writebacks are skipped. Lacks explicit alternatives or comparison to sibling tools.

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/ZengLiangYi/ChatCrystal'

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