Skip to main content
Glama
Sign In
engram-mcp

engram-mcp

by Cartisien
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

history

Retrieve the recent conversation history of a session, ordered chronologically. Specify the session ID and optional limit to get past messages.

Instructions

Get recent conversation history for a session in chronological order.

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": "history"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionIdYesSession identifier
limitNoMax entries (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description alone must disclose behavior. It indicates a read operation but does not mention side effects, authentication needs, rate limits, or output format. The description is straightforward but minimally transparent.

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 a single sentence of 10 words, highly concise and front-loaded with the core action. No wasted verbiage; every word earns its place.

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 list retrieval tool with two parameters and no output schema, the description covers the basic purpose. However, it lacks details like pagination, ordering direction (ascending/descending), or whether it returns full messages, which would improve completeness.

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%, meaning the schema already documents both parameters. The description adds no extra meaning beyond 'session identifier' and 'max entries (default 20)', so it provides little additional value.

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 verb 'Get', the resource 'conversation history', and the scope 'for a session', and specifies the order as chronological. It effectively distinguishes from sibling tools like 'recall' or 'recall_recent', which are not session-specific.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use for session-based history retrieval but provides no explicit guidance on when to use this versus sibling tools (e.g., recall, recall_by_time). No exclusions or alternatives are mentioned, leaving the agent to infer context.

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

Deploy Server

Other Tools