Skip to main content
Glama
mariusei

Scantool - File Scanner MCP

by mariusei
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Scan File Content

scan_file_content

Scans source content to return a line-numbered structural outline with signatures and condensed excerpts, revealing classes and functions for codebase exploration.

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. Content given directly (remote files, APIs, a git blob, stdin), same budget/depth and focus as scan_file. In your shell: sct scan - --as <path> or sct focus - --as <path> <name> (if sct is not on PATH, "/app/.venv/bin/python" -m scantool.cli replaces sct).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNobalanced
depthNo
focusNo
budgetNo
contentYes
condenseNo
filenameYes
output_formatNotree
show_complexityNo
show_decoratorsNo
show_docstringsNo
show_signaturesNo
include_metadataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.23.0
    • addedInput schema / properties / budget
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
    • addedInput schema / properties / condense
      Added value: +{
+  "default": true,
+  "type": "boolean"
+}
    • addedInput schema / properties / depth
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
    • addedInput schema / properties / focus
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
    • addedInput schema / properties / include_metadata
      Added value: +{
+  "default": true,
+  "type": "boolean"
+}
    • addedInput schema / properties / mode
      Added value: +{
+  "default": "balanced",
+  "type": "string"
+}
  2. Changed1 schema field changedv0.20.1
    • addedInput schema / additionalProperties
      Added value: +false
  3. First observedv0.19.4

TDQS

A4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses depth levels (quick ~300 tokens, normal 1500, deep everything), elision markers (⟨…⟩ +N), and that focus reads elided content. It provides shell command examples. However, it does not cover all behavioral aspects like exact output format or error handling. Substantial insight but not exhaustive.

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?

The description is dense but front-loaded with the main purpose. Each sentence adds detail about behavior, depth, or usage. It is not overly brief but is well-structured, with key information upfront and examples. It is appropriately sized for the tool's complexity.

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?

Given the tool has 13 parameters, no output schema, and no annotations, the description provides a fair amount of context: core behavior, depth options, shell usage. However, it leaves many parameters undefined and relies on 'same as scan_file' which may not be obvious to the agent. For a complex tool, it is not fully complete.

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 coverage is 0%, so the description must compensate. It explains the depth parameter (quick/normal/deep), focus (reads elided content), and budget (token counts implied). It does not describe mode, output_format, condense, show_* flags, or other parameters. It adds value for key parameters but does not cover the majority of the 13 parameters.

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 states it scans file content given directly (remote files, APIs, git blob, stdin) and produces a skeletal structure with path:line, signatures, and excerpts. It explicitly mentions 'Content given directly' and 'same budget/depth and focus as scan_file', which differentiates it from the sibling scan_file (which presumably uses file paths). This is a specific verb+resource with clear sibling differentiation.

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?

The description implies when to use this tool: when you have content directly rather than a file path. It provides shell command examples but does not explicitly name alternative tools or state 'use this instead of scan_file when providing content'. It gives clear context about the input type but lacks explicit exclusions.

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