Skip to main content
Glama
Sign In
SetLuca

SetLuca

Official
by setluca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Archive or restore memories

luca_memory_set_archived
DestructiveIdempotent

Archive or restore several memories at once. Archiving stops Luca using a fact while the record and its provenance survive, so it is always reversible.

Instructions

Archive or restore several memories at once. Archiving stops Luca using a fact while the record and its provenance survive, so it is always reversible.

Luca operation: POST /api/memory/bulk Required scopes: memory:write Required OAuth scope: luca:draft; data sensitivity: redacted Requires Idempotency-Key. Provide idempotencyKey for safe retries, or the server will generate one. Use workspaceId or workspaceSlug to override the default workspace configured by environment.

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": {
      "body": "<body>"
    },
    "name": "luca_memory_set_archived"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
workspaceIdNoOptional Luca workspace id override.
workspaceSlugNoOptional Luca workspace slug override.
idempotencyKeyNoStable key for safe retries. If omitted, the MCP server generates a unique key for this call.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description adds meaningful context beyond them: archiving is reversible because provenance survives, memory:write scope and luca:draft OAuth scope are required, and data sensitivity is redacted. It does not cover restore-side behavior or whether archived facts disappear from list results, so it falls short of a 5.

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?

Purpose is front-loaded in the first sentence and the remaining lines are structured metadata (endpoint, scopes, idempotency, workspace override) rather than filler. The block is slightly boilerplate-heavy but each line carries operational 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?

For a bulk mutation with auth scopes, idempotency, and workspace targeting, the description covers the operational prerequisites an agent needs; an output schema exists so return values need not be described. Minor residual gap: no note on partial failures or what happens to already-archived ids in a bulk call.

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 75%, and the description adds behavioral meaning to two params: idempotencyKey is optional because the server generates one, and workspaceId/workspaceSlug override the environment default. It adds nothing about the ids array bounds or the action enum, which the schema already handles.

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 a specific verb pair (archive/restore) and resource (several memories at once), making the bulk scope explicit. It is readily distinguishable from siblings like luca_memory_update and luca_memory_list without opening any schema.

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

Usage Guidelines3/5

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

It explains what archiving means semantically (Luca stops using the fact, record and provenance survive) which implies when to use it, but it never states when to prefer this over luca_memory_update or luca_memory_list, and gives no exclusions. Usage is implied rather than directed.

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