recall-kit

project_decide

Records a project decision with its rationale and source so teams can trace why choices were made and preserve context across sessions.

Instructions

Record a project decision together with WHY it was made.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>",
      "decision": "<decision>",
      "rationale": "<rationale>",
      "source": "<source>"
    },
    "name": "project_decide"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes
`source`	Yes
`decision`	Yes
`rationale`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations, the description carries the full burden. It implies a write but says nothing about whether entries are append-only or mutable, whether duplicates are allowed, what happens with an unknown slug, or whether the call has side effects beyond storage. An output schema exists so return structure need not be explained, but the write-behavior gaps remain significant.

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?

A single front-loaded sentence with no filler and the key differentiator (the rationale) emphasized. It is efficient, though the brevity is partly a symptom of under-specification rather than discipline.

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

Completeness2/5

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

Four required parameters, zero annotation coverage, and no schema descriptions leave too much unexplained: neither the identity/format of 'slug' nor the meaning of 'source' is discoverable. For a persistence tool with mandatory inputs, the definition should say more about what a valid call looks like.

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

Parameters2/5

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

Schema coverage is 0%, so the description must compensate. It adds real meaning for 'rationale' by framing it as the WHY, but leaves 'slug' (project identifier format?) and especially 'source' (a person, a document, a meeting?) completely undefined in both schema and description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: "Record a project decision," and adds the scope that the rationale is captured too. This clearly separates it from project_add/project_update, which operate on the project itself rather than on a decision record, though no sibling is named explicitly.

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

Usage Guidelines2/5

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

There is no guidance on when to call this versus project_update or memory_remember, and no mention of prerequisites such as whether the project slug must already exist. The agent must infer usage entirely from the tool name.

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

Deploy Server