Skip to main content
Glama

log_session

Save a session log as a new note in Claude/Sessions, index it in Claude/Index.md, and capture what happened, what was learned, and what was decided.

Instructions

Save a session log as a new note in Claude/Sessions/ and list it in Claude/Index.md. Call it when a meaningful piece of work ends, and say what happened, what was learned and what was decided.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title": "<title>",
      "content": "<content>",
      "project": "<project>"
    },
    "name": "log_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNo
titleYes
contentYes
projectYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It usefully discloses two side effects: creating a note under Claude/Sessions/ and updating Claude/Index.md, but it does not explain overwrite behavior, permissions, failure modes, or what the output contains.

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?

The description is two efficient sentences with no filler. It front-loads the concrete action and destination, then adds the usage trigger and content expectation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The output schema exists, so return values need less explanation, and the description covers purpose, timing, and side effects. However, for a mutation tool with no annotations and 0% schema description coverage, the lack of guidance on required fields like project and optional tags leaves important invocation details incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for four parameters, so the input schema provides no field-level meaning. The description hints that content should cover what happened, what was learned, and what was decided, but it says nothing about title, project, or tags, leaving most parameters undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: save a session log as a new note in Claude/Sessions/ and list it in Claude/Index.md. It is clear what artifact is created and where, but it does not differentiate itself from sibling write tools such as write_note or capture.

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?

The description gives a clear usage condition: call it when a meaningful piece of work ends. It does not state when not to use it or name an alternative tool for related note-writing tasks, so it falls short of full alternative routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.