Skip to main content
Glama
ZengLiangYi

ChatCrystal

by ZengLiangYi
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

recall_for_task

Retrieve reusable task memories before coding tasks. Load project-scoped memories and global lessons for implementation, debugging, migration, refactoring, configuration, investigation, or optimization.

Instructions

Retrieve reusable task memories before starting substantive coding work. Use this at the beginning of implementation, debugging, migration, configuration, investigation, refactor, or optimization tasks to load project-scoped memories first and optional global lessons second. Use mode="debug" when the user reports an error, failing command, regression, or incident; include error_signatures and related_files when available. Use search_knowledge instead for ad hoc semantic note search that is not tied to the current task. This tool is read-only and returns ranked memories plus optional related-note context without writing anything.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoUse task for normal work and debug when the task starts from an error, failing test, or incident.task
taskYesCurrent task context used to retrieve relevant project and global memories.
optionsNoOptional limits and relation expansion controls for recall results.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed16 schema fields changedv0.5.6
    • addedInput schema / properties / mode / description
      Added value: +"Use task for normal work and debug when the task starts from an error, failing test, or incident."
    • addedInput schema / properties / options / description
      Added value: +"Optional limits and relation expansion controls for recall results."
    • addedInput schema / properties / options / properties / global_limit / description
      Added value: +"Maximum number of cross-project/global lessons to append after project memories."
    • addedInput schema / properties / options / properties / include_relations / description
      Added value: +"Whether to include related-note context for returned memories."
    • addedInput schema / properties / options / properties / project_limit / description
      Added value: +"Maximum number of project-scoped memories to return first."
    • addedInput schema / properties / task / description
      Added value: +"Current task context used to retrieve relevant project and global memories."
    • addedInput schema / properties / task / properties / branch / description
      Added value: +"Current VCS branch when relevant to the task."
    • addedInput schema / properties / task / properties / cwd / description
      Added value: +"Current working directory of the agent session."
    • addedInput schema / properties / task / properties / error_signatures / description
      Added value: +"Concrete errors, stack traces, failing commands, or symptoms. Most useful with debug tasks."
    • addedInput schema / properties / task / properties / files_touched / description
      Added value: +"Files already touched or expected to be touched; improves project memory matching."
    • addedInput schema / properties / task / properties / goal / description
      Added value: +"Plain-language task goal or user request. Include enough context to retrieve relevant memories."
    • addedInput schema / properties / task / properties / project_dir / description
      Added value: +"Absolute project directory when known; helps ChatCrystal match memories to the right local workspace."
    • addedInput schema / properties / task / properties / project_key / description
      Added value: +"Stable project identifier used to prioritize project-scoped memories, such as a repository or workspace key."
    • addedInput schema / properties / task / properties / related_files / description
      Added value: +"Additional files related to the task but not necessarily modified."
    • addedInput schema / properties / task / properties / source_agent / description
      Added value: +"AI coding tool or agent that is calling ChatCrystal; use unknown when unsure."
    • addedInput schema / properties / task / properties / task_kind / description
      Added value: +"Kind of work being performed. Use debug for failures; choose the closest non-debug category for planned work."
  2. First observedv0.5.5

TDQS

A4.6/5.0
Behavior5/5

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

No annotations provided, so description carries full burden. It states the tool is read-only, returns ranked memories plus optional related-note context, and writes nothing. This sufficiently discloses behavioral traits without contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single paragraph that is front-loaded with purpose and well-structured. Every sentence adds value; no wasted words. Efficiently covers usage, mode, and exclusions.

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 complexity (3 parameters, nested object, no output schema), description explains return values (ranked memories plus optional context) and main use cases. Lacks details on exact output format but sufficient for agent understanding.

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 baseline is 3. The description adds some context (e.g., use debug mode for errors) but mainly restates schema information. No significant additional semantics beyond 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 clearly states the tool retrieves reusable task memories before starting substantive coding work, with specific verb ('Retrieve') and resource ('reusable task memories'). It distinguishes from sibling tool search_knowledge by specifying when to use that alternative.

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?

Provides explicit guidance on when to use (at beginning of implementation, debugging, etc.) and when not to (ad hoc note search via search_knowledge). Also gives mode-specific instructions (debug mode for errors) and lists optional parameters for context.

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