Skip to main content
Glama
SVerITG

Metis

by SVerITG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Metis · Memory Curator — Save Session Summary

save_session_summary

Persist a plain-English recap of what was discussed, decided, or built so future sessions can recall and search it. Stores key topics and decisions for cross-session continuity.

Instructions

Save a summary of the current session to persistent memory.

Call this at the end of any substantive session so future sessions can
recall what was discussed, decided, or built — the core of Metis's
cross-session continuity. The saved summary is searchable later via
search_session_memory and surfaces when you resume related work.

Args:
    summary: A 2–5 sentence, plain-English summary of what happened this
        session. Required.
    key_topics: Optional list of short topic tags for retrieval
        (e.g. ["phase-10", "APScheduler"]).
    decisions: Optional list of key decisions made
        (e.g. ["switched to AGPL-3.0"]).
    session_id: Optional identifier used to group related summaries; if
        omitted, the summary is stored on its own.
    client: Which Claude client this session ran in — 'code' (Claude Code),
        'chat' (Claude Desktop), or 'dashboard'. Lets the dashboard show a
        Code-vs-Desktop breakdown. Optional; defaults to unset.

Returns:
    A dict with the saved record's id and a confirmation status.

Input Schema

NameRequiredDescriptionDefault
clientNo
summaryYes
decisionsNo
key_topicsNo
session_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.5
    • addedInput schema / properties / client
      Added value: +{
+  "default": "",
+  "title": "Client",
+  "type": "string"
+}
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does a fair job: it discloses that the write is persistent, that the record is searchable later and resurfaces on related work, and what the call returns (id plus confirmation status). It omits whether repeat saves duplicate or overwrite, and any permission or retention considerations.

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?

Well front-loaded: purpose and timing first, then structured Args and Returns sections. A few phrases, notably "the core of Metis's cross-session continuity", are promotional filler rather than operational information, but the parameter block earns its length.

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?

Five parameters with zero schema documentation and no output schema, yet every parameter is described with semantics and examples and the return value is summarized. An agent has enough to invoke it correctly on the first attempt.

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?

Schema description coverage is 0%, so the description must supply everything, and it does: summary is constrained to 2–5 plain-English sentences, key_topics and decisions get concrete example values and purpose, session_id's grouping behaviour is explained including the omission case, and client enumerates code/chat/dashboard with the dashboard breakdown rationale.

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 ("Save a summary of the current session to persistent memory") and ties it to a named retrieval counterpart, search_session_memory. It does not differentiate from adjacent writers in the sibling list such as save_session_event, store_episodic_memory, or consolidate_session_memory, so an agent must infer the boundary from the noun 'summary'.

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?

Gives an explicit trigger — "Call this at the end of any substantive session" — and describes the downstream payoff (later recall via search_session_memory). No exclusion or 'do not use when' guidance against the other session-memory writers is offered, which is the one gap.

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

Deploy Server

Other Tools