Skip to main content
Glama
purmemo-ai

pūrmemo

Official
by purmemo-ai
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Hybrid

commit

Store completed PRDs, ADRs, specs, or OKRs as searchable commitment memories with optional target dates and key results, so decisions and promises persist across sessions and remain queryable by type.

Instructions

Persist a commitment-shaped artifact (PRD, ADR, spec, OKR) as a memory with intent='commitment'.

WHEN TO USE: This is the write primitive for /prd, /decide, /spec, /commit slash commands. Call after the artifact is fully drafted in the conversation. Send the COMPLETE artifact verbatim — do NOT summarize.

INSERT-only. Each call creates a new memory; supersede prior versions by recency, never overwrite. No conversationId parameter (intentional — see ADR-034).

QUERYABLE: GET /api/v1/commitments/?type= returns all commitments of a given type, filterable by target_date and sorted by recency.

EXAMPLES:

  • commit(title="ADR-035 - Foo - Bar - 2026-04-28", type="ADR", content="", key_result="single-sentence chosen-option statement")

  • commit(title="PRD - Email verification flow", type="PRD", content="", target_date="2026-05-15")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoOptional tags for categorization. "commitment" and the lowercased commitment_type are added automatically.
titleYesTitle following the pattern "[Type]-NNN - [Project] - [Subject] - [Date]" for ADRs, or "[Project] - [Type] - [Feature]" for PRDs/specs.
contentYesCOMPLETE artifact content, verbatim — the full markdown body of the PRD/ADR/spec/OKR.
key_resultNoOptional one-sentence concrete deliverable. What is true when this commitment is honored?
target_dateNoOptional target date in YYYY-MM-DD format. Omit if no deadline.
commitment_typeYesThe kind of commitment.

Tool Definition Quality

A4.9/5.0
Behavior5/5

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

The description reveals INSERT-only behavior, no overwrite, intentional lack of conversationId, and queryability via GET endpoint. This adds value beyond annotations (readOnlyHint=false, destructiveHint=false) and does not contradict them.

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?

The description is substantive and well-structured with sections (WHEN TO USE, INSERT-only, QUERYABLE, EXAMPLES). While slightly lengthy, every sentence adds value; no redundancy.

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?

Given the tool's complexity (6 params, no output schema), the description covers all necessary aspects: purpose, usage, parameters, behavior, and examples. It is self-contained and complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All 6 parameters have schema descriptions (100% coverage). The description adds context: title patterns, verbatim content requirement, key_result as single-sentence deliverable, auto-added tags. This enriches the schema beyond raw definitions.

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's purpose: persisting commitment-shaped artifacts (PRD, ADR, spec, OKR) as memories with intent='commitment'. It provides examples and distinguishes itself as the write primitive for specific slash commands, differentiating from siblings.

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?

The description explicitly states when to use (after artifact is fully drafted, for slash commands) and what not to do (do not summarize). It also clarifies insertion semantics (INSERT-only, never overwrite) and mentions queryability, providing clear guidance.

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/purmemo-ai/purmemo-mcp'

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