Skip to main content
Glama

temporal_stats

Analyze memory creation patterns over time, showing frequency and most active periods for a given session.

Instructions

Returns temporal statistics about when memories were created — frequency over time, most active periods.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionIdYesSession identifier

Implementation Reference

  • src/index.ts:233-243 (registration)
    Registration of the 'temporal_stats' tool in the ListToolsRequestSchema handler, defining its name, description, and input schema (sessionId required).
    {
      name: 'temporal_stats',
      description: 'Returns temporal statistics about when memories were created — frequency over time, most active periods.',
      inputSchema: {
        type: 'object',
        properties: {
          sessionId:  { type: 'string', description: 'Session identifier' },
        },
        required: ['sessionId'],
      },
    },
  • Input schema for temporal_stats: takes a sessionId string parameter.
      inputSchema: {
        type: 'object',
        properties: {
          sessionId:  { type: 'string', description: 'Session identifier' },
        },
        required: ['sessionId'],
      },
    },
  • Handler for the 'temporal_stats' tool in CallToolRequestSchema. Calls memory.temporalStats(sessionId) and returns the stats as JSON.
    case 'temporal_stats': {
      const stats = await (memory as any).temporalStats(args.sessionId as string);
      return { content: [{ type: 'text', text: JSON.stringify(stats, null, 2) }] };
    }
Behavior2/5

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

With no annotations provided, the description should disclose behavioral traits. It only states what the tool returns, but does not mention side effects (likely none), required permissions, rate limits, or any guarantees about ordering or accuracy. This is insufficient for full transparency.

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, efficient sentence with no wasted words. It conveys the core purpose without redundancy.

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?

Given the tool's simplicity (one parameter, no output schema), the description is adequate but incomplete. It does not describe the format of the returned statistics (e.g., array, object) or provide examples, leaving the agent to infer. It also omits prerequisites or permissions. Scores 3 as a minimum viable description.

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?

The schema description coverage is 100% for the single parameter 'sessionId', so the schema already provides meaning. The description adds no additional context about the parameter, such as clarifying that sessionId represents a user or session for which to retrieve memory statistics. Baseline 3 is appropriate given full schema coverage.

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 'Returns' and the specific resource 'temporal statistics about when memories were created', including concrete examples like 'frequency over time, most active periods'. This distinguishes it from sibling tools like 'stats' (likely more general) and 'user_stats'.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It does not mention when to use or avoid it, nor does it reference sibling tools like 'stats' or 'recall_by_time' that might offer similar functionality.

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/Cartisien/engram-mcp'

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