Projectmem

Overview Schema Source Related Servers Discussions Admin

add_note

Record gotchas, setup details, or other durable context that doesn't fit as an issue or decision. Prefix with gotcha:, lesson:, or warning: to enable cross-project auto-promotion and recall.

Instructions

Record a gotcha, setup detail, or other durable context.

Use when you discover something important that doesn't fit as an
issue or decision. Notes survive across sessions and appear in
wrap context blocks.

Side effects: appends a `note` event. Notes prefixed `gotcha:`,
`lesson:`, or `warning:` are eligible for auto-promotion to
~/.projectmem/global/ for cross-project recall (L-046).

Input Schema

TableJSON Schema

Name	Required	Description
`project`	No	Which project this call is about — a registered id, alias, or absolute path (e.g. 'ossdrop'). Omit it when the server was started for a single repo, or when an active project is set with `pjm project use`. Call list_projects to see the registered names.
`summary`	Yes	One-line description of the gotcha, setup detail, or context worth preserving. Prefix with 'gotcha:' or 'lesson:' to enable cross-project promotion — e.g., 'gotcha: bcrypt v4 silently truncates passwords longer than 72 bytes'.
`location`	No	Optional file path or library this note applies to (e.g., 'bcrypt' for a library-specific gotcha).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.3.2Sep 8, 2026

addedInput schema / properties / project

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Which project this call is about — a registered id, alias, or absolute path (e.g. 'ossdrop'). Omit it when the server was started for a single repo, or when an active project is set with `pjm project use`. Call list_projects to see the registered names.",
+  "title": "Project"
+}

Changed2 schema fields changedv0.1.3May 20, 2026

addedInput schema / properties / location / description

Added value: +"Optional file path or library this note applies to (e.g., 'bcrypt' for a library-specific gotcha)."

addedInput schema / properties / summary / description

Added value: +"One-line description of the gotcha, setup detail, or context worth preserving. Prefix with 'gotcha:' or 'lesson:' to enable cross-project promotion — e.g., 'gotcha: bcrypt v4 silently truncates passwords longer than 72 bytes'."

First observedv0.1.1May 19, 2026

TDQS

A4.9/5.0

Behavior5/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It clearly states the side effect: 'appends a `note` event.' It also discloses cross-session persistence, appearance in wrap context blocks, and auto-promotion rules for prefixed notes. This is unusually transparent for a write-like tool.

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 compact and front-loaded, with the core purpose in the first sentence. Every subsequent sentence earns its place: one gives usage timing, one gives side effects, and one explains promotion behavior. There is no filler or repetition of schema details.

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 simple three-parameter tool with a 100%-covered schema and an output schema, the description is complete. It explains why the note is durable, where it appears, what event it appends, and when to use it instead of issue/decision tools. An agent has enough context to select and invoke this tool correctly.

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 description coverage is 100%, so the baseline is 3. The description adds value by framing the summary as durable context rather than transient commentary and by including 'warning:' as an auto-promotion prefix, which goes beyond the schema's mention of only 'gotcha:' and 'lesson:'. It does not add much about project or location, but those are already well documented in 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?

The description opens with a specific verb and resource: 'Record a gotcha, setup detail, or other durable context.' It also explicitly distinguishes the tool from issue/decision tracking, which maps to the sibling tools log_issue and add_decision. This makes the tool's scope immediately clear and separates it from related tools.

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?

'Use when you discover something important that doesn't fit as an issue or decision' gives an explicit condition for use and an implicit exclusion: if it does fit as an issue or decision, use those instead. It also explains the persistence and visibility consequences ('survive across sessions and appear in wrap context blocks'), which helps the agent reason about when this tool is appropriate.

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

Deploy Server