Skip to main content
Glama

save_session_log

Record a coaching session log at session end, capturing the most important takeaway, flags raised, decisions made, and plan adjustments.

Instructions

    Save a session summary log for today.

    Called at the end of a coaching session to persist what was discussed.
    The summary should be 3-5 lines covering: what was discussed, flags
    raised, decisions made, and any plan adjustments.

    IMPORTANT: The first line should be a standalone sentence capturing
    the session's most important takeaway, as it will be used as a
    one-liner in compressed session history.

    Args:
        summary: The session summary text (3-5 lines).
        coach_name: Name of the coach persona used in this session.

    Returns:
        Confirmation message.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
summaryYes
coach_nameNoCoach

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Describes write operation and return confirmation. No annotations, so description covers behavioral aspects adequately. Lacks details on idempotency or overwrite behavior.

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?

Concise, well-structured with purpose, usage, and parameter details. No redundant information.

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?

Simple tool with two parameters and output schema; description covers purpose, usage, parameters, and return value adequately.

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?

With 0% schema description coverage, the description fully explains both parameters: summary format (3-5 lines, key takeaway first) and coach_name (purpose and default).

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?

Clear verb 'save', resource 'session summary log', and context 'for today' at end of coaching session. Distinct from sibling read tools like get_session_logs.

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?

Specifies when to call ('at end of coaching session') and format requirements (3-5 lines, first-line takeaway). Does not explicitly exclude alternatives or mention when not to use.

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/wernerpe/mcpacer'

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