Penfield Memory

list_artifacts

Read-only

List artifacts in a directory.

Returns the immediate contents of a directory (not recursive).
Separates folders and files for easy navigation.

Args:
    path_prefix: Directory path to list (default: "/")
    name_pattern: Optional case-insensitive substring filter on file/folder names

Returns:
    Formatted directory listing or error message

Examples:
    >>> await list_artifacts("/")
    {'success': True, 'path': '/', 'folders': [...], 'files': [...]}

    >>> await list_artifacts("/", name_pattern="readme")
    {'success': True, 'path': '/', 'folders': [], 'files': [{'name': 'readme.md', ...}]}

Input Schema

TableJSON Schema

Name	Required	Description	Default
`path_prefix`	No		/
`name_pattern`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedApr 22, 2026

addedInput schema / properties / name_pattern

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Name Pattern"
+}

First observedMar 16, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations declare readOnlyHint and openWorldHint. The description adds behavioral context: non-recursive listing and separation of folders/files. No contradiction with 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 concise, well-structured with a summary, parameter docs, return type, and examples. Every sentence adds value without redundancy.

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?

The description includes a clear return format and examples, compensating for the output schema not being provided. It covers the tool's functionality sufficiently for a list operation.

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

Parameters5/5

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

With 0% schema description coverage, the description compensates by explaining both parameters: path_prefix as default '/' and name_pattern as optional case-insensitive filter. This adds meaning beyond the schema's type and default.

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 artifacts in a directory and returns immediate contents non-recursively, separating folders and files. This specific verb and resource distinction differentiates it from sibling tools like explore or search.

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

Usage Guidelines4/5

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

While the description implies usage for listing directory contents and shows examples, it does not explicitly state when to use this tool over siblings like explore or search. The purpose is clear but lacks explicit when-not-to-use guidance.

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

All Penfield Memory tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.