Skip to main content
Glama
Sign In
Mnemonic

Mnemonic

by bacharyehya
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

mnemonic_create

Create a new memory to persist important information across sessions. Add tags and trigger phrases so the memory surfaces when relevant topics appear.

Instructions

Create a new memory.

Use this to store important information that should persist across sessions. Memories can be tagged for organization and have trigger phrases that surface them when relevant topics come up.

Example: - Title: "Bash's communication style" - Content: "Direct, concise, no fluff. Lead with conclusions." - Tags: ["preferences", "user-profile"] - Triggers: ["how does bash like responses"]

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "params": "<params>"
    },
    "name": "mnemonic_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYesInput for creating a new memory.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It adds useful context about persistence ('persist across sessions') and trigger-based surfacing ('surface them when relevant topics come up'). However, it does not disclose any side effects, permissions, or error behaviors, though for a create operation this is minimal. The description does not contradict any structured data.

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?

The description is tight and front-loaded, starting with the core purpose. The example is well-structured and earns its place by concretely demonstrating usage. Every sentence contributes meaning, with no fluff or redundancy.

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 output schema exists and the input schema covers all parameters, the description is sufficiently complete. It covers the core use-case, provides an illustrative example, and explains memory behaviors like persistence and triggering. It might not mention edge cases or limitations, but the schema and output schema handle the rest, so nothing critical is missing.

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?

The schema provides 100% parameter descriptions, so the baseline is 3. The description adds value by presenting a complete example with realistic values for title, content, tags, and triggers, illustrating how to use the parameters in practice. It also conceptually explains how tags and triggers work, which enriches understanding beyond the 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 opens with 'Create a new memory,' which is a specific verb and resource, clearly distinguishing it from sibling tools like mnemonic_update or mnemonic_delete. The example further confirms the agent's understanding of what 'create' entails, 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 Guidelines4/5

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

The description says 'Use this to store important information that should persist across sessions,' providing clear context on when to invoke the tool. It does not explicitly mention alternatives or when not to use it, but the 'create' operation is self-evident versus siblings. This matches 'clear context, no exclusions'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools