Skip to main content
Glama
Sign In
engram-mcp

engram-mcp

by Cartisien
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

daily_summary

Return a summary of memories for a specified date, defaulting to today if omitted.

Instructions

Returns a summary of memories for a given date (YYYY-MM-DD), or today if omitted.

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

Input Schema

NameRequiredDescriptionDefault
sessionIdYesSession identifier
dateNoISO date string YYYY-MM-DD (optional, defaults to today)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior2/5

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

No annotations provided, so description bears full burden. It mentions 'returns a summary' but does not disclose any behavioral traits such as read-only nature, potential side effects, or what the summary includes. Minimal 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?

Single sentence of 15 words, front-loaded with purpose. No wasted information. Perfectly concise for the tool's simplicity.

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 (2 params, no output schema) and the range of sibling tools, the description covers the basic functionality. However, it lacks detail on what the summary contains (e.g., count, types) and doesn't differentiate from similar tools.

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 coverage is 100% with descriptions for both parameters. Description adds no extra meaning beyond the schema (e.g., the date format and default are already in schema). Baseline 3 applies.

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?

Clearly states verb 'Returns', resource 'summary of memories', and specifies date handling (YYYY-MM-DD or today). Distinguishes from sibling tools like recall or history by focusing on a daily summary.

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?

Implies use for obtaining a daily memory summary, but lacks explicit guidance on when not to use it or mention of alternatives like recall_by_time. No exclusions or context provided.

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