Skip to main content
Glama
Sign In
Vestige

Vestige

by samvallad33
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

protect

Pin a memory to prevent automatic merging, superseding, or garbage collection. Set protected=false to unpin and allow normal memory lifecycle.

Instructions

Pin a memory so it can never be auto-merged, superseded, or garbage-collected. Pass protected=false to unpin.

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": "protect"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMemory id to protect/unprotect.
protectedNotrue to pin (block auto-merge/supersede/forget), false to unpin. Default true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.6.0
  2. Removedv2.3.0
  3. First observedv2.1.27

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It explains the protective effect and the toggle for unpinning. It does not discuss permissions, errors, or return values, but the core behavior and reversibility are clearly communicated.

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, each earning its place: the first states the core action and guarantees, the second explains the reversal. The content is front-loaded and free of filler.

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 simple two-parameter toggle tool with no output schema, the description plus schema covers the essential use, semantics, and reversal. It is complete enough for an agent to invoke correctly, though it leaves response/error behavior unspecified.

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%, and the schema already documents both id and protected, including the default and meaning. The description's 'Pass protected=false to unpin' adds no new meaning beyond the schema, so it meets the baseline but does not exceed it.

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 uses the specific verb 'Pin' and clearly identifies the resource: a memory. It also states the exact consequences (no auto-merge, supersede, or garbage-collection), which distinguishes it from sibling tools like merge_candidates, plan_supersede, and gc.

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?

The description implies when to use the tool: when a memory should be preserved from automatic maintenance. However, it does not explicitly state when not to use it or mention any alternatives, leaving some usage reasoning to inference.

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