knowl

Overview Schema Source Related Servers Discussions Admin

knowl_session_finish

Finish a manual memory session you own, record its outcome, and optionally promote captures to project memory. Avoid hook-owned sessions, which finalize themselves.

Instructions

Finish and optionally promote a manual memory session you explicitly own. Never call this for a hook-owned session: when verified lifecycle hooks are active they finalize it themselves, and finishing it here closes a session out from under them.

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": {
      "sessionId": "<sessionId>",
      "status": "<status>"
    },
    "name": "knowl_session_finish"
  }
}

Input Schema

Name	Required	Description
`status`	Yes	How the session ended. failed still records what was learned.
`promote`	No	Whether to promote the session's captures into project memory. Defaults to false.
`summary`	No	Durable summary of what the session established.
`sessionId`	Yes	Memory session ID you started and own.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv5.23.0Sep 16, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations provide only openWorldHint=false, so the description carries most of the behavioral burden. It discloses the potentially harmful consequence of finishing a hook-owned session and clarifies that 'failed' status still records learning via the schema. It does not describe output behavior, but that is less critical here.

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?

Two sentences with no filler. The key scoping condition ('you explicitly own') is front-loaded, and the warning about hook-owned sessions is placed exactly where it adds value.

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?

For a tool with four well-described parameters and no output schema, the description covers the essential contextual distinction: manual ownership vs hook ownership. It could mention the effect of 'promote' more explicitly, but the schema already documents that parameter.

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%, and each parameter already has a clear description. The tool description adds context around 'own' and 'promote', but it does not add meaningful semantics beyond the schema, so baseline 3 is appropriate.

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?

Description states a specific verb ('Finish') and resource ('manual memory session you explicitly own') and further clarifies the optional 'promote' behavior. It also distinguishes this tool from hook-owned session handling, making it easy to differentiate from sibling tools.

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?

It gives explicit when-to-use guidance: manual sessions you own. It also clearly says when not to use it (hook-owned sessions), explaining that lifecycle hooks finalize themselves. No explicit alternative tool is named, but the exclusion is unambiguous and actionable.

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