Skip to main content
Glama

Metis · Memory Curator — Commit Session Decisions

commit_session_decisions

Capture and store session decisions permanently. Enforces at least one concrete decision per session, writing each to episodic memory for future retrieval.

Instructions

Commit key decisions from this session to permanent memory.

This is the mandatory recording checkpoint — call it at the end of every
agent-routed session, before delivering the final result to the user.
Unlike save_session_summary (which accepts any summary), this tool enforces
that at least one concrete decision is captured, and writes each decision
separately to episodic_memory for future retrieval.

Args:
    decisions: 1-5 plain-English decisions made this session. Be specific:
        "Chose logistic regression over mixed model due to data sparsity in
        Zone de Santé X" not "made a modelling decision".
    summary: 1-3 sentence summary of the session context (optional but useful).
    key_topics: Topic tags e.g. ["DHIS2", "domain surveillance", "tracker design"].
    session_id: Optional session identifier.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
summaryNo
decisionsYes
key_topicsNo
session_idNo
Behavior4/5

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

With no annotations, the description carries full burden. It discloses that the tool enforces at least one decision, writes to episodic memory, and requires concrete decisions. It does not mention side effects or permissions, but provides adequate transparency for a write operation.

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 well-organized with a clear front-loaded purpose, usage note, and parameter list. It is slightly verbose but every sentence adds value. Could be slightly more concise, but still effective.

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?

Given 4 parameters, no output schema, and no annotations, the description covers the tool's role, when to call, parameter details, and storage behavior. It provides sufficient context for an agent to use the 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 0%, so description must compensate. It explains the decisions parameter with examples, notes summary's optionality, describes key_topics as tags, and session_id as optional. This adds significant meaning beyond the schema structure.

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 verb 'commit', the resource 'key decisions from this session', and explicitly distinguishes from the sibling tool 'save_session_summary' by noting its enforcement of at least one decision and separate episodic memory storage.

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?

Provides explicit when to use: 'at the end of every agent-routed session, before delivering the final result'. Also gives an alternative tool ('save_session_summary') and explains the difference.

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/SVerITG/Metis'

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