Skip to main content
Glama

connect_project_folder

Register all relevant files in a project folder for Metis to read. Recursively scans for recognized extensions and adds them to the tracked files table, enabling later retrieval.

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?

No annotations are provided, so the description carries the full burden. It discloses recursive walking, recognized extensions, and the max_files safety limit, but does not cover idempotency, error handling, or authentication needs. The description adds value beyond the schema but is not comprehensive for a mutation tool.

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 concise, using four well-structured sentences: main purpose, details on recursion and extensions, usage instruction, then parameter list. Every sentence adds value with no redundancy.

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 (recursive folder walk, extension list, three parameters) and the presence of an output schema (not shown), the description is fairly complete. It explains what the tool does, how to use it, and parameters. Missing details like error handling or idempotency are minor gaps.

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

Parameters4/5

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

Schema description coverage is 0%, yet the description provides clear explanations for all three parameters: folder_path (absolute path), label (short label), and max_files (safety limit with default). This adds significant meaning beyond the schema's type/default info, compensating for the lack of schema descriptions.

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 registers all relevant files in a project folder so Metis can read them, specifying the verb 'register', the resource 'project folder', and the outcome 'files added to tracked_files table'. It distinguishes from sibling tools like read_file by providing post-use instructions.

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

Usage Guidelines5/5

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

The description explicitly says 'Call this once per project; after that, use read_file() to read any individual file', providing clear when-to-use and when-not-to-use guidance with an alternative named.

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_PH'

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