Skip to main content
Glama
dl4rce

flaiwheel

by dl4rce
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

save_session_summary

Append a session summary to your project's session log. Record accomplishments, decisions, and next steps for future sessions.

Instructions

Append a session summary to the project's session log.

    Side effects: appends a JSON entry to /data/sessions-{project}.json.
    Does not modify the vector index or the knowledge repo. Safe to call
    multiple times in one session — each call adds a new entry.

    Call at the END of every session. Use get_recent_sessions() at the
    START of the next session to restore context.

    Args:
        summary: What was accomplished this session (1–3 sentences)
        decisions: Key decisions made, comma-separated (optional)
        open_questions: Unresolved questions or next steps, comma-separated (optional)
        files_modified: Files changed, comma-separated (optional)
        project: Target project name (optional)

    Returns:
        Confirmation with the project name and total session count stored.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
summaryYes
decisionsNo
open_questionsNo
files_modifiedNo
projectNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A5/5.0
Behavior5/5

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

Discloses side effects: appends JSON to a specific file, does not modify vector index or knowledge repo, safe to call multiple times, and each call adds a new entry. With no annotations, this fully covers behavioral expectations.

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?

Well-structured with clear sections: purpose, side effects, usage guidance, args, returns. Front-loaded with core action, every sentence adds value without 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?

With 5 parameters, 1 required, and an output schema mentioned, the description provides complete context: side effects, usage pattern, return value (confirmation with project and session count), and parameter guidance. No gaps.

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?

Despite 0% schema description coverage, the description includes detailed parameter documentation for all 5 parameters (e.g., 'summary: What was accomplished this session (1–3 sentences)'), adding meaning far beyond the bare 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?

The description clearly states the action 'Append a session summary to the project's session log' and differentiates from the sibling tool 'get_recent_sessions' by providing usage guidance.

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?

Explicitly states 'Call at the END of every session' and suggests using 'get_recent_sessions()' at the start of next session, providing clear when-to-use and alternatives.

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/dl4rce/flaiwheel'

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