Skip to main content
Glama
zihin-ai

Zihin MCP Server

by zihin-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

list_agent_memory

Read-onlyIdempotent

Retrieve and paginate an agent's stored memories, including facts, preferences, instructions, and context, filtered by category or user key.

Instructions

Lista memórias persistentes de um agente. Retorna fatos, preferências, instruções e contexto armazenados.

Input Schema

NameRequiredDescriptionDefault
limitNoMáximo de memórias por página (default 50)
beforeNoPaginação: `updated_at` do último item da página anterior
agent_idYesUUID do agente
categoryNoFiltrar por categoria de memória
user_keyNoFiltrar por user_key específico (identifica o usuário final)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.2.2
    • addedInput schema / properties / before
      Added value: +{
+  "description": "Paginação: `updated_at` do último item da página anterior",
+  "type": "string"
+}
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "fact",
-  "preference",
-  "instruction",
-  "context",
-  "schedule_report"
-]New value: +[
+  "fact",
+  "preference",
+  "instruction",
+  "context"
+]
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Máximo de memórias por página (default 50)",
+  "maximum": 200,
+  "minimum": 1,
+  "type": "integer"
+}
  2. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds only that memories are persistent and enumerates the stored categories; it says nothing about ordering, cursor semantics, or default page size behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the verb and resource. The second sentence restates the category enum already present in the schema, a minor redundancy, but overall there is no wasted text.

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?

With no output schema, the description should carry more of the return contract; it names the categories but omits ordering, cursor-based pagination semantics (before = updated_at of last item), and the 200-item cap. Annotations cover the safety dimension, so the remaining gap is moderate rather than severe.

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?

Schema description coverage is 100%, so every parameter (limit, before, agent_id, category, user_key) is already documented in the schema, including the enum and the default of 50. The description adds no extra parameter meaning, making the baseline 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Lista memórias persistentes de um agente') and enumerates the memory categories returned (fatos, preferências, instruções, contexto), which maps directly to the enum. It is clearly distinguishable from delete_agent_memory, but it never explicitly contrasts with sibling list/read tools.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no note about pagination order, and no mention of how this relates to the sibling delete_agent_memory or to per-agent reads. Usage is only inferable from the verb 'Lista'.

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