Hebbrix MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

hebbrix_list

Read-onlyIdempotent

Retrieve recent memories from a collection to review what an AI agent has stored. Specify the collection and limit to control how many entries are returned.

Instructions

List recent memories in a collection.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "hebbrix_list"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`collection_id`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.3Jul 9, 2026

TDQS

B3.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the main behavioral aspects. The description adds minimal extra context (recent, collection) without contradicting annotations.

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, clear sentence with no unnecessary words. It is well-structured and directly to the point.

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

Completeness2/5

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

Despite having an output schema, the description is minimal. It does not explain what 'memories' or 'collection' refer to, nor does it provide any filtering or pagination details beyond the parameter names. The overall context is insufficient for a complete understanding.

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

Parameters1/5

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

The parameters limit and collection_id are not explained in the description. With zero schema descriptions, the description fails to clarify their purpose or constraints, leaving the agent without adequate information.

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 action (list), the resource (memories), and the scope (recent, in a collection). It effectively distinguishes from sibling tools like hebbrix_get or hebbrix_search.

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?

The description does not indicate when to use this tool versus alternatives such as hebbrix_search or hebbrix_history. It lacks contextual guidance on appropriate use cases or boundaries.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.