Skip to main content
Glama
Sign In
claude-crowed

claude-crowed

by TheNewJavaman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

memory_update

Update a stored memory by creating a new version, keeping the old version archived and out of search results. Get the new version ID.

Instructions

Update an existing memory, creating a new version. The old version is preserved but removed from the search index. Returns the new version's ID.

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": {
      "id": "<id>"
    },
    "name": "memory_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
titleNo
contentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Beyond a simple 'update', the description reveals versioning behavior, preservation of old version, removal from search index, and return of new version ID. This adds significant transparency not covered by annotations.

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?

Two sentences with no filler. Front-loaded with purpose and key behavioral notes. Every sentence adds value.

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

Completeness2/5

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

Despite good behavioral detail, the description omits parameter explanations and usage context. With 3 parameters and no output schema, it should provide more field-level guidance.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage, yet the description does not explain any parameter semantics. It fails to describe the role of 'id', 'title', or 'content' beyond basic schema types.

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 updates an existing memory, creating a new version, and distinguishes from siblings like memory_store or memory_delete. It uses a specific verb and resource.

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 explicit guidance on when to use this tool vs alternatives such as memory_store or memory_delete. The description implies updating, but lacks context or exclusion criteria.

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