Skip to main content
Glama

commit_session_decisions

Record key decisions from any session to permanent memory, ensuring at least one concrete decision is captured 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
Behavior3/5

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

With no annotations, description discloses writing to episodic_memory, enforcing at least one decision, and separate storage per decision. However, lacks details on idempotency, overwrite behavior, or side effects.

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-structured with summary first, then usage context, then parameter details. Slightly verbose but each sentence adds value. Could tighten the 'mandatory recording checkpoint' phrasing.

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 params, no output schema, and no annotations, the description adequately covers usage workflow (end-of-session), parameter constraints, and examples. Missing return value is acceptable without output schema.

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 coverage is 0%, but description's Args section adds meaningful constraints and examples: decisions (1-5, specific), summary (1-3 sentences, optional), key_topics (tag format), session_id (identifier). Adds significant value beyond raw schema types.

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 clearly states the verb 'commit' and resource 'key decisions from this session to permanent memory'. It explicitly contrasts with sibling tool 'save_session_summary', distinguishing its purpose.

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?

Explicitly instructs to call at end of every agent-routed session before delivering final result. Provides clear when-to-use and differentiates from save_session_summary, though doesn't address other related siblings.

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