Skip to main content
Glama

connect_project_folder

Registers all relevant files in a project folder for Metis to read. Walks the folder recursively to add files with supported extensions (code, markdown, data).

Instructions

Register all relevant files in a project folder so Metis can read them.

Walks the folder recursively and adds every file with a recognised extension
(.R, .Rmd, .md, .py, .js, .ts, .sql, .json, .yaml, .qmd, .tex, .csv) to
the tracked_files table. Call this once per project; after that, use
read_file() to read any individual file.

Args:
    folder_path: Absolute path to the project root folder.
    label: Short label for all files from this project (e.g. "MLM Course").
    max_files: Safety limit — stop after registering this many files (default 200).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folder_pathYes
labelNo
max_filesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations provided, the description must fully disclose behavior. It explains recursion, recognized extensions, and the safety limit (max_files). However, it omits details like error handling (e.g., nonexistent folder), duplicate file registration, or side effects beyond adding to the tracked_files table. The description is transparent about core behavior but lacks depth.

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 two short paragraphs plus a bulleted argument list. Every sentence contributes essential information. The main purpose is in the first sentence, and the usage guideline follows immediately. No unnecessary words or details.

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?

Given the tool's complexity (3 parameters, no enums, output schema exists), the description is largely complete: it covers purpose, parameters, and usage pattern. It does not repeat output schema details (allowed per guidelines). However, it lacks information on prerequisites (e.g., folder must be accessible) and error conditions, which would improve completeness.

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?

Schema description coverage is 0%, meaning the description carries full weight. It provides clear, actionable explanations for all three parameters: folder_path (absolute path), label (short label with example), and max_files (safety limit with default). This adds significant value beyond the schema's minimal type/title information.

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's purpose: 'Register all relevant files in a project folder so Metis can read them.' It specifies the action (register), resource (files in a project folder), and scope (relevant files with recognized extensions). This distinguishes it from siblings like 'scan_folder_for_intent' or 'scan_project_folder' by focusing on registration for later reading.

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 advises calling the tool once per project and then using read_file() to read individual files, establishing a clear workflow. However, it does not explicitly compare itself to sibling tools (e.g., 'scan_project_folder') or state when not to use this tool, which limits guidance on tool selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SVerITG/Metis'

If you have feedback or need assistance with the MCP directory API, please join our Discord server