Skip to main content
Glama

session_mine

Mine past coding sessions to search conversations, find decisions, replay file discussions, detect struggles and errors, correlate edits, and generate timelines and summaries.

Instructions

Mine session history. Operations:

  • search: Search across past conversations (query, project_path, limit, method=hybrid|semantic|keyword)

  • decisions: Find when/why a decision was made (query, project_path)

  • replay: Find discussions about a file (file_path, project_path)

  • struggles: Files/areas with repeated difficulty (project_path)

  • errors: Recurring error patterns across sessions (project_path)

  • correlations: Files always edited together (project_path)

  • timeline: Project development timeline (project_path)

  • summaries: Auto-generated session summaries (project_path)

  • overview: High-level project stats (project_path)

  • status: Mining index coverage (project_path)

  • reindex: Trigger background re-indexing (project_path, mode=post_session|bootstrap|full)

  • predict: Predict context needed for a file edit (file_path, project_path)

  • cross_project: Patterns across all projects (no project_path needed)

  • reflect: LLM-powered analysis of mistakes, patterns, and decisions (project_path)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationYesOperation to perform
project_pathNoProject directory
queryNoFor search/decisions: search query
file_pathNoFor replay: file to find discussions about
limitNoMax results (default 10)
methodNoFor search: search method
modeNoFor reindex: mining mode
sinceNoFor search: filter after date (YYYY-MM-DD)
untilNoFor search: filter before date (YYYY-MM-DD)
Behavior2/5

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

No annotations are provided, so the description bears full responsibility. It describes what each operation does but fails to disclose behavioral traits such as side effects (e.g., reindex modifies state), authorization needs, or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is structured as a bulleted list within a paragraph, making it scannable. It front-loads the main purpose, but the list is lengthy (14 items) and could be more concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (14 operations, 9 parameters, no output schema), the description covers every operation and its associated parameters comprehensively, providing a complete picture of the tool's capabilities.

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

Parameters4/5

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

With 100% schema coverage, the description adds value by grouping parameters per operation (e.g., 'for search/decisions: query') and clarifying which parameters apply to which operation, going beyond the schema's flat descriptions.

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 'Mine session history' and enumerates 14 distinct operations with specific verbs (search, decisions, replay, etc.), correctly distinguishing from sibling tools like scout_search or memory.

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 lists operations but does not provide explicit guidance on when to use this tool versus alternatives. Usage is implied through operation names, but no when-not-to or comparison to siblings is given.

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/20alexl/claude-engram'

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