Skip to main content
Glama
mariusei

Scantool - File Scanner MCP

by mariusei
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List Directories

list_directories

Lists folders in a directory tree to reveal project structure. Use to explore directory hierarchy without cluttering output with files.

Instructions

Skeleton of files or a directory: every structure with path:line, signature or title, a condensed excerpt within the budget. A directory gives the tree with one-line gists. --depth quick is about 300 tokens per file, normal 1500, deep everything with module values whole (files only). Elided content is marked ⟨…⟩ +N; focus reads it. Folders only, no files: the directory hierarchy. Answers: read a file's contents; outline of a file; list the functions and classes in a file; read or show the source of one function, method or class by name. In your shell: sct --help (if sct is not on PATH, "/app/.venv/bin/python" -m scantool.cli replaces sct).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
directoryYes
max_depthNo
respect_gitignoreNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.20.1
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv0.19.4

TDQS

C2.1/5.0
Behavior2/5

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

The description discloses some behavior, such as 'Elided content is marked ⟨…⟩ +N' and depth-based token budgets, but it is inconsistent (e.g., 'Skeleton of files' vs. 'Folders only, no files') and does not clarify side effects, permissions, or the exact output shape. With no annotations, the description carries full burden and fails to give a coherent behavioral picture.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long, rambling, and mixes tool-specific behavior with generic CLI usage instructions ('In your shell: sct --help'). It is not front-loaded; the core operation is buried in the middle. Every sentence does not earn its place, and the irrelevant CLI help paragraph should be removed.

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

Completeness2/5

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

For a tool with 3 parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain what the returned tree looks like, how max_depth affects output, or how respect_gitignore changes behavior. The mention of elision markers is useful but not enough to make the tool safely callable.

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

Parameters1/5

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

Schema description coverage is 0%, so the description must detail all three parameters (directory, max_depth, respect_gitignore) but does not. It vaguely mentions '--depth quick' and token budgets without mapping to the max_depth parameter, and it never addresses respect_gitignore. This is a critical gap for an agent to invoke the tool correctly.

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

Purpose3/5

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

The description suggests this tool lists a directory tree with one-line gists ('A directory gives the tree with one-line gists') and claims 'Folders only, no files', but it opens with a vague phrase about 'skeleton of files or a directory' that muddies the resource. It does not explicitly state the verb+resource in a focused way nor differentiate from siblings like scan_directory or preview_directory.

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

Usage Guidelines2/5

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

No explicit when-to-use or alternative-selection guidance is provided. The 'Answers:' section lists general capabilities of an underlying CLI tool, not conditions for choosing this tool over its siblings. The only implicit hint is 'Folders only, no files', which is not framed as a decision rule.

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

Deploy Server

Other Tools