Skip to main content
Glama
alopez3006

snipara-mcp

by alopez3006

snipara_end_of_task_commit

Persist end-of-task summary, structured why capture, and outcomes for agent handoff. Validate via dry_run without writing.

Instructions

Persist a bounded end-of-task summary, optional structured Why Capture, and selected durable outcomes so another agent can resume the work. This EDITOR operation writes memory and workflow state and is non-idempotent; dry_run validates without writing. Use snipara_remember_if_novel for one reusable memory and document upload tools for source material. Unknown fields fail closed. Returns created or skipped records, review candidates, handoff metadata, and validation warnings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
whyNoAtomic Why Capture payload; never split by summary heuristics
taskNoShort task label used as structured Why Capture provenance
dry_runNoValidate extraction and return the proposed receipt without writing memory or workflow state.
outcomeNoFinal task state used to frame the handoff and durable extraction.completed
summaryNoUnstructured task summary used only when why is absent
categoryNoOptional stable category shared by memories produced from this commit.
artifactsNoDurable artifact identifiers or paths produced by the task.
handoff_onlyNoFor final workflow commits, create the Team Sync handoff and skip durable-memory extraction.
files_touchedNoProject-relative files materially changed or inspected during the task.
persist_typesNoMemory categories that may be extracted from the task summary; omit unwanted categories.
external_user_idNoIntegrator client keys only: stable end-user ID for user-owned memories created from task commits.
memory_reconciliation_modeNoFor newly created task memories, find older similar memories. recommend returns candidates only; auto_safe supersedes only high-confidence same-scope/type/category matches.recommend
Behavior5/5

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

The description clearly states it is an EDITOR operation that writes memory and workflow state, is non-idempotent, and that unknown fields fail closed. This adds significant behavioral context beyond annotations, which only provide hints about read-only, open-world, idempotent, and destructive nature.

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?

The description is concise at four sentences, front-loaded with the primary purpose, and every sentence adds value. No redundant or wasted text.

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?

Given the complexity of the tool (12 params, nested objects, no output schema), the description provides essential context: it explains return values, validation behavior, and alternative tools. It could be slightly more detailed, but overall it is adequately complete for an experienced agent.

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?

The input schema has 100% description coverage for all 12 parameters, so the baseline is 3. The description adds minimal parameter-specific meaning beyond the schema, but the schema itself is comprehensive. No deduction needed.

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 persists end-of-task summaries, structured Why Capture, and durable outcomes for agent handoffs. It distinguishes from siblings by naming snipara_remember_if_novel for single reusable memories and document upload tools for source material.

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

Usage Guidelines4/5

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

The description explicitly mentions when to use snipara_remember_if_novel and document upload tools as alternatives. It also notes dry_run validates without writing, giving guidance on validation usage. However, it does not explicitly state when not to use this tool versus the named alternatives.

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