Skip to main content
Glama
alopez3006

snipara-mcp

by alopez3006

snipara_remember_if_novel

Idempotent

Store a memory only when it is novel compared to existing reviewed memories, with automatic deduplication and optional supersede of similar records.

Instructions

Store one durable Memory V2 record only when it is sufficiently different from existing reviewed memory. This EDITOR operation may write project, team, user, or agent state; duplicate calls normally skip the write, while auto_safe reconciliation may supersede high-confidence same-owner matches without deleting them. Use snipara_end_of_task_commit for multi-outcome workflow capture and context tools for source documents. Returns whether storage occurred, duplicate evidence, the memory ID, and reconciliation actions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesThe memory text to store
typeNoDurable knowledge type used for authority, retention, and later recall filtering.fact
scopeNoMemory owner boundary. scope=agent requires agent_id; scope=user is personal to the authenticated user or integrator external_user_id.project
sourceNoOptional source label for the memory write
agent_idNoRequired when scope=agent; identifies the agent-owned memory namespace
categoryNoOptional stable category used to group and deduplicate related memories.
ttl_daysNoOptional retention period in days; omit only for knowledge that should not expire automatically.
related_toNoExisting memory IDs that provide an explicit relationship, not duplicate candidates.
dedupe_limitNoMaximum nearest existing memories examined before deciding whether this write is novel.
document_refsNoProject-relative source document paths supporting this memory; never place secrets here.
allow_supersedeNoReserved for future conflict handling
external_user_idNoIntegrator client keys only: stable end-user ID for scope=user memory. Snipara hashes and namespaces it per integrator client.
novelty_thresholdNoSimilarity threshold above which a memory is treated as duplicate
memory_reconciliation_modeNoAfter storing, find older similar memories. recommend returns supersede candidates only; auto_safe supersedes only high-confidence same-scope/type/category matches. No physical deletion.recommend
Behavior5/5

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

Discloses behavioral traits beyond annotations: conditional storage based on novelty, duplicate skipping, auto_safe reconciliation superseding high-confidence matches without deletion, and potential state writes. Annotations provide idempotent and non-destructive hints, but the description adds nuanced behavior not captured in 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?

Concise, front-loaded with core purpose, and every sentence adds essential information. No fluff or repetition. Length is appropriate given the tool complexity.

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?

Despite 14 parameters and no output schema, the description is highly complete: it explains core logic (novelty, deduplication, reconciliation), scope semantics, return fields (storage status, duplicate evidence, memory ID, reconciliation actions), and references sibling tools. Covers all critical aspects for correct invocation.

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%, so baseline is 3. The description does not significantly add parameter-level meaning beyond the schema. While it provides context like 'never place secrets here' for document_refs, this is also in the schema. No major added value.

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 'Store one durable Memory V2 record only when it is sufficiently different from existing reviewed memory.' It specifies it is an EDITOR operation, distinguishes from snipara_end_of_task_commit and context tools, and lists return values. The name and description together convey a precise verb-resource-action.

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 advises using snipara_end_of_task_commit for multi-outcome workflow capture and context tools for source documents, indicating when not to use this tool. It also describes duplicate call behavior and reconciliation modes, providing clear guidance on when the tool is appropriate.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/alopez3006/snipara-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server