Skip to main content
Glama
Claude Free Code MCP

Claude Free Code MCP

by ImIpscanning

project_tree

Read-only

List a bounded directory tree to inspect workspace structure, excluding heavy dependency folders by default. Configure target folder, nesting depth, and hidden entries.

Instructions

List a bounded directory tree. Excludes heavy dependency directories by default.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "project_tree"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxDepthNoMaximum nesting, 1..20
directoryNoRelative folder to scan.
includeHiddenNoInclude hidden entries

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds a genuinely useful behavior detail, that heavy dependency directories are excluded, but 'bounded' is never quantified (no entry cap or truncation behavior), and 'by default' suggests an override switch that no parameter provides.

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?

Two short sentences with no filler, and the core operation is front-loaded ahead of the exclusion caveat. Nothing could be removed without losing information.

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

Completeness3/5

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

All three optional parameters are schema-documented and safety is annotation-covered, so the basics are present. However, for a traversal tool the description leaves the practical limit unexplained — what 'bounded' means in output size, whether results are truncated, and what the tree representation looks like — which is the main thing an agent needs before calling it.

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% — maxDepth, directory and includeHidden are each documented in the schema. The description does not elaborate on default-relative paths, the 1..20 depth range, or what hidden entries cover, so it adds no meaning beyond the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List a bounded directory tree') and adds a scope modifier ('bounded') that distinguishes it from a plain file glob. It does not name a sibling such as glob_files or list_snapshots to draw a contrast, so it stops short of a 5.

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?

Usage is only implied by the operation itself: an agent can infer this is for surveying directory structure. There is no explicit when-to-use, when-not-to-use, or pointer to alternatives like glob_files for pattern matching, so guidance is thin.

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