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

ai-memory-mcp

by zhanpu89
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_summary_by_id

Read-onlyIdempotent

Retrieve a specific conversation summary by providing its unique session ID.

Instructions

根据 session_id 精确查询单条摘要记录。

Args: params (GetSummaryByIdInput): 包含： - session_id (str): 目标会话 ID

Returns: Dict: {"success": bool, "data": 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": "get_summary_by_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already provide readOnlyHint, destructiveHint, and idempotentHint. The description adds that it queries exactly one record and returns a dict with 'success' and 'data', but does not clarify behavior if the ID is not found. No contradictions.

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—one sentence for purpose, then structured Args/Returns blocks. No unnecessary words. Front-loaded with the core action.

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

Completeness4/5

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

For a simple query tool with one parameter and an output schema, the description covers the basics. It could clarify behavior when the ID does not exist, but overall sufficient.

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?

Schema coverage is 0%, but the description explicitly documents the single parameter (session_id) with type and description, adding meaning beyond the schema's minimal constraints. However, no examples or edge-case details.

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 explicitly states '根据 session_id 精确查询单条摘要记录' (exactly query a single summary record by session_id), which is a specific verb-resource combination that clearly distinguishes this tool from siblings like search_summaries or list_recent_sessions.

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

Usage Guidelines4/5

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

The description implies usage when a specific session_id is known and a single record is needed, but does not explicitly state when not to use or mention alternatives like search_summaries for multiple results. Some guidance is present.

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