perseus

perseus_tree

Read-only

Displays a directory tree with configurable depth for understanding project structure at a glance.

Instructions

Display a directory tree with configurable depth. Use to understand project structure at a glance. For flat file listings with metadata, use perseus_list instead. Read-only; depth limits control output size.

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": {
      "path": "<path>"
    },
    "name": "perseus_tree"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes	Directory path for tree display (default: workspace root)
`depth`	No	Value for depth parameter

Output Schema

Name	Required	Description	Default
`root`	No	Root directory path
`tree`	No	Directory tree as formatted text

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.0.10Jun 27, 2026

changedInput schema / properties / depth / description

Previous value: -"Maximum depth for directory tree traversal"New value: +"Value for depth parameter"

addedInput schema / properties / path

Added value: +{
+  "description": "Directory path for tree display (default: workspace root)",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[]New value: +[
+  "path"
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "root": {
+      "description": "Root directory path",
+      "type": "string"
+    },
+    "tree": {
+      "description": "Directory tree as formatted text",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedv1.0.7Jun 10, 2026

changedInput schema / properties / depth / description

Previous value: -"depth= modifier for @tree"New value: +"Maximum depth for directory tree traversal"

First observedv0.1.0May 27, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true; description adds 'Read-only' and 'depth limits control output size', providing extra behavioral context beyond 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?

Three clear, front-loaded sentences: action, usage context, sibling alternative and behavioral property. No wasted words.

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?

Covers purpose, usage, sibling differentiation, read-only behavior, and output size control; minor omission: lacks specification of default depth behavior, but output schema exists to supplement.

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?

Schema description coverage is 100% with both parameters described; description adds 'configurable depth' and 'depth limits control output size' but does not specify default depth or format, providing marginal added value.

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 uses specific verb 'Display a directory tree' and resource, and distinguishes from sibling perseus_list by contrasting with flat file listings.

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?

Explicitly states when to use ('understand project structure at a glance') and when to use alternative perseus_list for flat file listings; no other exclusions mentioned.

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