Skip to main content
Glama
arjunkmrm

Mem0 MCP Server

by arjunkmrm
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

list_entities

View which users, agents, apps, or runs currently hold stored memories in the Mem0 memory system to track memory ownership and access.

Instructions

List which users/agents/apps/runs currently hold memories.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • src/mem0_mcp_server/server.py:371-378 (handler)
    The list_entities tool handler function, which is registered via @server.tool decorator. It resolves the Mem0 API settings, gets the client, and calls client.users to list all entities (users/agents/apps/runs) with memories.
    @server.tool(description="List which users/agents/apps/runs currently hold memories.")
def list_entities(ctx: Context | None = None) -> str:
    """List users/agents/apps/runs with stored memories."""

    api_key, _, _ = _resolve_settings(ctx)
    client = _mem0_client(api_key)
    return _mem0_call(client.users)
  • src/mem0_mcp_server/server.py:371-371 (registration)
    Registration of the list_entities tool using the @server.tool decorator in the FastMCP server instance.
    @server.tool(description="List which users/agents/apps/runs currently hold memories.")

Tool Definition Quality

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It describes a read operation ('List') but does not disclose behavioral traits like whether it requires authentication, rate limits, pagination, or what the output format looks like, leaving significant gaps.

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 a single, efficient sentence that front-loads the purpose without unnecessary words, making it appropriately sized and zero waste.

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

Completeness3/5

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

Given the tool's complexity (simple list operation), no annotations, and an output schema (which handles return values), the description is minimally adequate. However, it lacks details on behavioral context like permissions or output structure, leaving room for improvement.

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?

The tool has 0 parameters with 100% schema coverage, so no parameter documentation is needed. The description does not add param info beyond the schema, but this is acceptable given the lack of parameters, warranting a baseline score above 3.

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 clearly states the specific action ('List') and the resource ('which users/agents/apps/runs currently hold memories'), distinguishing it from siblings like get_memories or search_memories that focus on memory content rather than entity holders.

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 identifying memory holders, but does not explicitly state when to use this tool versus alternatives like get_memories or delete_entities, nor does it provide exclusions or prerequisites.

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/arjunkmrm/mem0-mcp'

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