Skip to main content
Glama

add_tracked_file

Register a file for change monitoring, surfacing it on the Planning tab. Optionally assign a label.

Instructions

Add a single file to the tracked-files list and start watching it.

Registers one file so Metis notices when it changes and can read it later
via read_file; tracked files surface on the dashboard's Planning tab. The
file's current modification time is recorded and watch is set on. Re-adding
an existing path updates it (and keeps the old label unless a new one is
given). To register a whole project at once, use connect_project_folder.

Args:
    path: Absolute path to the file to track; the file must exist or an
        error is returned.
    label: Optional category label for the file (default empty string);
        on re-add, an empty label leaves the existing label unchanged.

Returns:
    A confirmation message naming the tracked file (and its label, if any),
    or a "file not found" / error message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
labelNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations present, so description carries full burden. It discloses key behaviors: file watching, recording modification time, re-adding behavior, error on missing file. However, lacks details on how watching works or potential side effects (like overwriting label rules). Still covers most important aspects.

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?

Description is well-structured with summary, details, args, and returns. Slightly lengthy but each sentence adds value. Could be tightened slightly.

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

Completeness5/5

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

Given simple tool with 2 params and existence of output schema, description covers purpose, usage, parameters, return value, and edge cases (re-adds, missing file). Complete for expected usage.

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 has 0% description coverage, but description compensates fully: explains path must be absolute and file must exist, label is optional and behavior on re-add. Adds meaning beyond schema.

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?

Description starts with specific verb ('Add a single file') and resource ('tracked-files list'), immediately distinguishing it from sibling tools like connect_project_folder. Clearly states what the tool does and how it differs.

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?

Explicitly tells when to use this tool (single file) and when not ('To register a whole project at once, use connect_project_folder'). Provides clear context for usage.

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