Skip to main content
Glama
r-darwish

daruma

by r-darwish
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

store_lesson

Store a lesson learned from your current development context by providing a title, content, optional scope, and tags.

Instructions

Stores a learned lesson based on the current directory context.

Parameters:
  - directory: The absolute path of the current workspace directory (REQUIRED).
  - title: Descriptive title of the lesson
  - content: Full lesson body (markdown format)
  - scope: Can be 'component' (folder-level), 'repository' (project-wide), or 'global' (cross-project rules)
  - tags: Optional comma-separated categories (e.g. "concurrency, mutex")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNo
scopeNocomponent
titleYes
contentYes
directoryYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

B3.4/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. Only says 'stores' but lacks details on side effects, overwriting behavior, or required permissions.

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?

Concisely lists parameters in a clear block. No extraneous sentences, but could be more structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Describes parameters adequately but omits return value or confirmation of success. With 5 parameters and no usage guidance, it feels minimally complete.

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 explains all 5 parameters with additional context (e.g., 'markdown format' for content, enum values for scope). Compensates well.

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?

States 'Stores a learned lesson' with a clear verb and resource. Differentiates from sibling read/search tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives. Does not explain prerequisites or typical use cases.

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/r-darwish/daruma'

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