Skip to main content
Glama

commit_session_decisions

Record key decisions from a session to permanent memory. Each decision is stored separately with context and topic tags 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
decisionsYes
summaryNo
key_topicsNo
session_idNo
Behavior4/5

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

With no annotations, description carries full burden. Discloses mandatory recording checkpoint, enforcement of at least one decision, and separate writes to episodic_memory. Could add details on idempotency or overwrites, but sufficient for safe use.

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?

Efficient structure: summary sentence, usage context paragraph, then bulleted args. Every sentence adds value. No redundancy.

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 4-param tool with no output schema and no annotations, description covers all parameters, usage timing, sibling differentiation, and behavioral expectations. No gaps for correct invocation.

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 has 0% description coverage; description compensates with rich guidance: decisions must be 1-5 plain-English with example, summary optional but structured, key_topics with example tags, session_id optional. Adds meaning beyond 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?

Starts with a clear verb+resource: 'Commit key decisions from this session to permanent memory.' Explicitly differentiates from sibling tool save_session_summary by noting this tool enforces decisions and writes to episodic_memory, making purpose distinct.

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?

Directly states when to use: 'call it at the end of every agent-routed session, before delivering the final result to the user.' Contrasts with save_session_summary, providing clear alternative. No guessing needed.

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_PH'

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