Skip to main content
Glama
Sign In
ai-memory-mcp

ai-memory-mcp

by zhanpu89
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_recent_sessions

Read-onlyIdempotent

Retrieve recent conversation session summaries, filterable by project name and branch name.

Instructions

列出最近的会话摘要，支持按项目和分支过滤。

Args: params (ListRecentSessionsInput): 包含： - limit (int): 最大返回条数，默认 10 - project_name (Optional[str]): 项目名称过滤，精确匹配 - branch_name (Optional[str]): 分支名称过滤，精确匹配

Returns: Dict: {"success": bool, "data": List[Dict]}

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": {
      "params": "<params>"
    },
    "name": "list_recent_sessions"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations indicate readOnlyHint=true, destructiveHint=false, and idempotentHint=true, which are correctly reflected. The description adds context about listing recent session summaries and filtering, aligning with the safe, non-destructive behavior. While it does not disclose additional traits like rate limits or auth, it provides adequate transparency beyond annotations.

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 concise with a clear introduction and a bulleted list for parameters. Every sentence adds value, and the structure facilitates quick understanding. No wasted words.

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?

The description covers the tool's purpose, parameters, and return format (success and data). With an output schema present and annotations defining safety, the description is complete for a simple listing tool. No gaps.

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 description explains all parameters (limit, project_name, branch_name) with details like default values and exact matching. However, the input schema already contains the same descriptions (e.g., '最大返回条数', '精确匹配'), so the description adds minimal new meaning. Schema coverage is effectively high, so baseline score of 3 is appropriate.

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 name 'list_recent_sessions' and description '列出最近的会话摘要' clearly state the verb (list) and resource (recent session summaries). The description explicitly mentions filtering by project and branch, making the purpose specific and distinguishable from siblings that search or manage summaries.

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 usage for retrieving recent sessions with optional filters but does not explicitly state when to use this tool versus alternatives like 'search_summaries' or 'get_summary_by_id'. No 'when not' or conflict resolution guidance is 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