The Same Platform Gives Its Tool Catalog BM25 and Its Memory Store ls
Overflow is a single problem, more candidates than fit and a need to hand back the ones that matter, and the Claude Developer Platform answers it one way for tools and a different way for memory. One problem, two surfaces A tool catalog overflows when the definitions cost more context than the task is worth. A memory store overflows for the same reason, and the platform documents the scale. A…
The Claude Developer Platform handles two overflow scenarios differently: tools and memory. When tools overflow, the platform uses ranked search with BM25 and regex-based search by default. In contrast, for memory, the platform provides a directory listing without ranking capabilities. The tool search tool uses regex-based and BM25-based search, returning up to 5 tool references by default.
Memory stores, on the other hand, hold up to 10,000 memories, with a List memories endpoint returning between 1 and 100 items per page, with a default limit of 20. The retrieval process for memory stores is based on stable, server-defined ordering, unlike the ranked selection on the tool side. The distinction in retrieval design forces the model to read the listing to decide what is relevant.
The practical consequence is that tool authors should use clear, descriptive definitions for better discovery accuracy. Memory management best practices focus on store count and volume rather than naming conventions for paths, leaving the selection keys to the developers. The endpoint is marked Beta and has a dated header, with all the information above being probed on 2026-09-07.
There is no indication that the platform cannot search memory; it only states that the documented List memories endpoint has no search parameter. The endpoint's Beta status and dated header do not prove the platform's lack of search functionality for memory.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
