Skip to main content
Glama
wusaki0723

Aelios

by wusaki0723
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

memory_pin

Save a moment as a pinned, permanent memory that appears in memory_boot and is never deduplicated, decayed, or auto-deleted. Use for self-contained entries, not ordinary facts.

Instructions

Save a moment as a precious entry: pinned, offered through memory_boot (which shows the 20 most recent), and never deduplicated, decayed or deleted by the automatic pipeline. Each call creates a new entry. Write the content so it still makes sense on its own later, and attach the surrounding messages via context_message_ids. For ordinary facts use memory_upsert. Returns { data: precious record }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYesThe moment to keep, self-contained and readable on its own.
namespaceNoMemory space to use. Defaults to 'default'. Ignored when the API key is bound to a fixed namespace.
context_message_idsNoIds of stored messages (e.g. message_ids from memory_ingest) to keep as surrounding context.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.2
    • addedInput schema / properties / content / description
      Added value: +"The moment to keep, self-contained and readable on its own."
    • addedInput schema / properties / context_message_ids / description
      Added value: +"Ids of stored messages (e.g. message_ids from memory_ingest) to keep as surrounding context."
    • addedInput schema / properties / namespace / description
      Added value: +"Memory space to use. Defaults to 'default'. Ignored when the API key is bound to a fixed namespace."
  2. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the annotations: pinned, surfaced through memory_boot (20 most recent), never deduplicated/decayed/deleted by the automatic pipeline, and each call creates a new entry. This discloses durability and lifecycle behavior that annotations (which only say not read-only, not idempotent) do not convey.

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?

Three dense sentences, front-loaded with the core behavior, then usage guidance, then the alternative tool, then return shape. Every clause carries information; no filler.

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

Completeness5/5

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

For a 3-parameter write tool with no output schema, it covers lifecycle (durable, pinned), discoverability (memory_boot), non-idempotency (new entry each call), and return shape. Nothing essential 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?

Schema coverage is 100%, so baseline is 3. The description adds meaning beyond the schema by explaining the purpose of context_message_ids (attach surrounding messages) and the self-contained writing requirement for content, though it doesn't expand namespace semantics 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?

States a specific verb (Save/pin) and resource (a moment/precious entry) and distinguishes itself from siblings by naming memory_upsert as the tool for ordinary facts. An agent can tell this apart from memory_upsert or memory_ingest without opening schemas.

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

Usage Guidelines5/5

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

Explicitly says when to use it vs the alternative: 'For ordinary facts use memory_upsert.' It also gives a usage instruction for the content ('write so it still makes sense on its own later') and the routing via context_message_ids.

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