boltwork-mcp

memory_list

List all keys stored for your agent, optionally filtered by prefix, to discover stored context without retrieving values.

Instructions

List all keys stored for your agent, optionally filtered by prefix. Useful for discovering stored context without fetching values. Free — no Lightning payment required.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "agent_id": "<agent_id>"
    },
    "name": "memory_list"
  }
}

Input Schema

Name	Required	Description	Default
`agent_id`	Yes	Agent identifier
`prefix`	No	Filter keys starting with this prefix (optional)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.22May 28, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are present, so the description must disclose behavioral traits. It does state that the tool is 'free' and requires 'no Lightning payment,' which adds transparency. However, it does not discuss rate limits, data volume, or error behavior, leaving gaps for a read-only list operation.

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 three sentences, all delivering value: first states the core function, second provides use-case context, third adds cost insight. It is front-loaded and every sentence earns its place.

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

Completeness4/5

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

Given the simplicity of the tool (2 simple params, no output schema, no nested objects), the description covers the key aspects. It explains the purpose, filtering option, and cost. However, it does not specify the output format (e.g., list of key strings) which would improve completeness.

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?

With 100% schema description coverage, the baseline is 3. The description mentions 'optionally filtered by prefix' which mirrors the schema's prefix parameter but adds no additional meaning beyond what is already in the schema for agent_id or prefix.

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 tool lists all keys stored for the agent, optionally filtered by prefix. 'List all keys' is a specific verb+resource, and it distinguishes itself from sibling tools like memory_retrieve (fetch values) and memory_delete by focusing on discovery without fetching values.

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 provides implicit usage context: 'useful for discovering stored context without fetching values.' It hints at when to use (to explore available keys) but does not give explicit when-not-to-use or alternatives like memory_retrieve. The guidance is implied rather than stated.

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

Deploy Server