Skip to main content
Glama

Recent interactions

get_recent_interactions

Lists recently captured raw interactions newest first, optionally filtered by kind or session, to audit history or review events before distilling memory. Supports limit to control rows.

Instructions

List recently captured raw interactions (newest first) as [id] ts [kind] content lines. Optionally filter by kind. Use for auditing history or before distilling memory.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_recent_interactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoFilter by kind (prompt / tool_call / error)
limitNoMax rows (default 20, max 100)
sessionIdNoFilter by captured session id (default: all sessions)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.4.2
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed1 schema field changedv2.4.0
    • addedInput schema / properties / sessionId
      Added value: +{
      +  "description": "Filter by captured session id (default: all sessions)",
      +  "maxLength": 200,
      +  "type": "string"
      +}
  3. First observedv2.2.1

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose ordering and the return line format, and 'List' implies a non-mutating read, but it says nothing about volume, truncation, whether content is full or previewed, or any privacy/permission constraints on captured interaction content.

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 short sentences, front-loaded with what is returned and in what format before the use case. Nothing is redundant or padded.

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?

For a three-optional-parameter read tool with no output schema, the description usefully compensates by specifying the returned line format. The only real gap is silence on result volume and on the sessionId filter, which matters when logs can be long.

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

Parameters3/5

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

Schema description coverage is 100%, so all three parameters (kind, limit, sessionId) are already documented in the schema, including the enum and the limit range. The description only echoes the kind filter and adds no new meaning for limit or sessionId, so the baseline of 3 applies.

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?

It states a specific verb and resource ('List recently captured raw interactions') and adds ordering ('newest first') plus the exact output line shape '[id] ts [kind] content lines'. It implicitly separates itself from the memory siblings by emphasizing 'raw' interactions, but never names search_history or get_context as the alternative.

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?

'Use for auditing history or before distilling memory' supplies a clear use context, which is more than most tools offer. It stops short of exclusions or naming which sibling to use instead when the agent wants semantic search rather than a raw chronological dump.

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