Engram

List Sessions

engram_list_sessions

Read-onlyIdempotent

Find an exact session_id before recovery, closing or a handoff. Unlike engram_rehydrate, this lists bounded metadata without replaying journal content or changing a session. Returns JSON sessions with member/client attribution, status, activity and checkpoint availability, plus next_cursor.

Default scope=mine lists this member's sessions; scope=workspace explicitly includes teammates in the authenticated workspace. repo/status/agent_tool/member_id filter results; a teammate member_id requires workspace scope. limit defaults to 20, maximum 50. Pass next_cursor unchanged to continue newest-started-first pagination. Empty results are valid. Consumes daily call quota. OAuth: memory:read.

Input Schema

Name	Required	Description
`repo`	No	Repository slug, e.g. engram or billing-api, within the authenticated workspace. This is a memory filter, not a filesystem path or workspace selector.
`limit`	No	Page size, default 20; from 1 to 50.
`scope`	No	Default mine lists your sessions across clients; workspace includes shared teammate session metadata.
`cursor`	No	Opaque next_cursor from the prior response. Keep filters unchanged; omit for the first page.
`status`	No	Filter journal state; omit to include both active and closed sessions.
`member_id`	No	Member id to filter; another member requires scope=workspace. This is a filter, not authorization.
`agent_tool`	No	Calling client name for attribution, e.g. codex, claude-code, cursor, or gemini. Omit if unknown.

Output Schema

Name	Required	Description
`text`	Yes	The same bounded payload as content[0].text; interpret it using format. JSON text contains the endpoint-specific fields described by this tool.
`format`	Yes	Payload encoding: Markdown context/checkpoint, serialized JSON data, or plain confirmation text.
`truncated`	Yes	True when the payload exceeded 120,000 characters and was cut with a notice. Narrow the request; truncated JSON is not parseable.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 20, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover readOnly/idempotent/non-destructive, and the description adds context annotations cannot express: it consumes daily call quota, requires the memory:read OAuth scope, and that member_id is a filter rather than authorization. It also discloses pagination ordering (newest-started-first) and the cursor contract.

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?

Purpose and the sibling contrast are front-loaded, then scope, filters, pagination, quota and auth follow in a logical order. Dense but each sentence carries distinct operational information; it runs slightly long for a list tool.

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?

With 7 optional params, an output schema, and full annotations, the remaining agent questions are answerable: what it returns, how to page, what it costs, and what auth it needs. Nothing needed for correct invocation is missing.

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 every parameter is already documented; the description largely restates defaults (scope=mine, limit 20/50) and the member_id+workspace coupling that the schema also states. Baseline 3 is appropriate since the schema carries the parameter burden.

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?

States a specific verb+resource ('lists bounded metadata' of sessions) and gives the concrete job it serves: 'Find an exact session_id before recovery, closing or a handoff.' It explicitly separates itself from the nearest sibling, engram_rehydrate, so an agent can route without opening either schema.

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

Usage Guidelines5/5

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

Names the alternative (engram_rehydrate) and the discriminating condition (bounded metadata, no journal replay, no session mutation). It also warns that empty results are valid, preventing a retry loop.

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

All Engram tools Inspect

Try in Browser

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?