Leapfrog MCP

Session Action History

session_memory

Retrieve recent actions performed in a browser session, useful for recovering context after compression.

Instructions

Recall what actions were performed in this session. Useful after context window compression to recover lost context.

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": {
      "sessionId": "<sessionId>"
    },
    "name": "session_memory"
  }
}

Input Schema

Name	Required	Description	Default
`sessionId`	Yes
`limit`	No	Number of recent actions to return. Default: 20.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.6.1Apr 8, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states recall without explaining read-only nature, error handling, or data ordering. This is minimal for a tool with no annotations.

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?

Two sentences, each valuable. The first states purpose, the second gives a usage hint. No fluff, front-loaded, and efficient.

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?

For a simple tool with 2 params and no output schema, the description covers purpose and one use case. However, it lacks details on return format, ordering, or failure behavior, making it merely adequate.

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?

The input schema has 50% coverage (limit described, sessionId not). The description does not mention or elaborate on any parameters, failing to add meaning beyond the schema. Given low coverage, the description should compensate.

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 tool's purpose: 'Recall what actions were performed in this session.' This distinguishes it from sibling tools like session_create or session_destroy by focusing on history recall.

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 provides a use case: 'Useful after context window compression to recover lost context.' It doesn't specify when not to use or name alternatives, but the sibling context implies this is the dedicated recall tool.

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