Skip to main content
Glama
thuupx

memory-mcp-lite

by thuupx

Get project memory summary

get_project_summary
Read-onlyIdempotent

Retrieve a concise summary of the project's architecture, key decisions, and conventions to provide project-level context.

Instructions

Return the concise summary for the current project (architecture, key decisions, conventions). USE WHEN: the request depends on project-level context — architecture, conventions, long-term decisions, or project overview. DO NOT USE WHEN: the request is about the current task's state, global preferences, or is self-contained. CALL ORDER: prefer this before search_memory_light. Pass workspace_path OR git_root OR remote_url OR project_id so the server can identify the project. RETURNS: { project_id, found, summary? } where summary has { id, title, summary, updated_at }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
git_rootNoAbsolute path to the git repository root
project_idNoExplicit project id (skip auto-resolution when known)
remote_urlNoGit remote URL, e.g. https://github.com/org/repo
workspace_pathNoAbsolute path to the workspace root, e.g. /Users/me/code/app

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
foundYes
summaryYes
project_idYes
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint. Description adds context about project identification method (one of four parameters) and return structure, including that summary contains id, title, summary, updated_at. 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?

Description is well-structured with clear sections (USE WHEN, DO NOT USE WHEN, CALL ORDER, RETURNS). Every sentence adds value, no redundancy. Front-loaded with core purpose.

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 rich annotations (readOnlyHint, idempotentHint) and presence of output schema, the description covers all essential aspects: purpose, usage conditions, parameter guidance, and return structure. No obvious gaps.

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

Parameters5/5

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

Schema coverage is 100%, but description adds crucial information: parameter selection logic (can pass workspace_path OR git_root OR remote_url OR project_id) and explains when to use project_id (explicit vs auto-resolution). This goes beyond the schema's individual parameter 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?

Description uses specific verb 'Return' and resource 'project summary', listing content (architecture, key decisions, conventions). It distinguishes from siblings like get_task_summary and get_global_summary by specifying project-level context.

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?

Explicitly includes 'USE WHEN' and 'DO NOT USE WHEN' sections with concrete conditions. Provides 'CALL ORDER' recommending preference over search_memory_light, giving clear guidance for agent decision-making.

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/thuupx/memory-mcp-lite'

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