metrecept-opensource

Cache: List cache trees

metrecept_list_cache_trees

Lists all isolated exact-replay cache trees a tenant owns, including main first with status, so you can find the tree_id needed by other cache tools. Optionally includes archived trees.

Instructions

List every cache tree (isolated exact-replay namespace) the tenant owns, always including the default "main", ordered main first then by creation time. All trees come back in one call. Each tree reports its status: active, frozen or archived. Use it to find a tree_id for the other cache tools. Not for a tree's contents: use metrecept_list_cache_entries. To create, fork or promote use metrecept_manage_cache_tree; to remove a non-main tree use metrecept_delete_cache_tree. Archived trees are hidden unless include_archived=true. Read-only, not billed, live. Requires a Metrecept API key (METRECEPT_API_KEY env on stdio, or Authorization: Bearer on remote HTTP); results are scoped to that key's tenant only.

Input Schema

Name	Required	Description	Default
`include_archived`	No	Also list archived trees (hidden by default). Default false.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.4.1Oct 25, 2026

addedInput schema / properties / include_archived

Added value: +{
+  "default": false,
+  "description": "Also list archived trees (hidden by default). Default false.",
+  "title": "Include Archived",
+  "type": "boolean"
+}

Addedv0.1.4Oct 25, 2026

TDQS

A4.8/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and does so: read-only, not billed, live, single-call complete results, default tree always included, archived hidden by default, and exact auth requirements (METRECEPT_API_KEY on stdio, Bearer on HTTP) plus tenant scoping.

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?

Front-loaded with purpose, ordering, and return shape before branching into alternatives and auth. Dense but nearly every clause carries information; the auth/tenant sentence could arguably be split or trimmed given it is boilerplate across the family.

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

Completeness5/5

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

An output schema exists so return-value detail is unnecessary, and the description still covers everything an agent needs: what comes back, how it is ordered, what statuses exist, how to get a tree_id, and what not to use it for.

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?

Schema coverage is 100%, so baseline is 3; the description goes slightly beyond by stating the observable effect of the flag ("Archived trees are hidden unless include_archived=true"), which frames the parameter as a visibility toggle rather than just a boolean name.

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?

States a specific verb+resource ("List every cache tree") plus the scope constraint (tenant-owned) and the ordering guarantee (main first, then creation time). The parenthetical "isolated exact-replay namespace" disambiguates what a cache tree is relative to the many other Metrecept resources.

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

Usage Guidelines5/5

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

Explicitly routes the agent: "Use it to find a tree_id for the other cache tools," then names exclusions with the correct sibling for each — metrecept_list_cache_entries for contents, metrecept_manage_cache_tree for create/fork/promote, metrecept_delete_cache_tree for removal.

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