list_memories
List memory metadata to browse stored memories. Filter by repository name for scoped results.
Instructions
List memory metadata.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| repo_name | No |
List memory metadata to browse stored memories. Filter by repository name for scoped results.
List memory metadata.
| Name | Required | Description | Default |
|---|---|---|---|
| repo_name | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description should disclose behavioral traits. It only states 'list memory metadata' without mentioning pagination, safety, or output details.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is too brief (3 words) and under-specified, lacking necessary detail for effective tool use.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the lack of output schema and annotations, the description fails to explain what is returned, any filtering, or how to interpret results.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description does not explain the repo_name parameter or its purpose.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'List memory metadata' clearly states the verb and resource, but it does not distinguish from sibling tools like read_memories or read_memory, which could also list memory data.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool vs alternatives like read_memories. No context on prerequisites or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/MSR806/agent-memory-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server