Skip to main content
Glama

update_file_metadata

Track file purpose, type, complexity, and dependencies to ensure accurate project understanding and efficient dependency management.

Instructions

Track important file metadata for project understanding and dependency management.

This tool provides flexible project lookup. You can specify any combination of identifiers, and it will resolve to the matching project.

Priority: project_id > workspace_path > project_name

WHEN TO USE:

  • After creating new files to document their purpose and relationships

  • When you understand a file's dependencies on other files

  • To update complexity assessments as files grow

  • To organize files into logical modules

  • When refactoring changes file dependencies

RECOMMENDED FOR: Key architectural files, complex modules, files with many dependencies. This helps build a dependency graph and understand the codebase structure.

FILE TYPES:

  • "source": Production code files (default)

  • "test": Test files and test suites

  • "config": Configuration files (package.json, .env, etc.)

  • "doc": Documentation files (README, docs, etc.)

COMPLEXITY LEVELS:

  • "low": Simple files, straightforward logic, minimal dependencies

  • "medium": Moderate complexity, some business logic, several dependencies

  • "high": Complex files, intricate logic, many dependencies, high cognitive load

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
moduleNoLogical module/component this file belongs to (optional) - e.g., "auth", "ui", "api"
purposeNoBrief description of what this file does (optional)
file_pathYesPath of the file (required) - e.g., "src/components/Button.tsx"
file_typeNoType of file - "source", "test", "config", or "doc" (default: "source")source
complexityNoComplexity level - "low", "medium", or "high" (default: "low")low
dependentsNoList of files that import/depend on this file (optional)
project_idNoProject ID from create_project() (optional if project_name or workspace_path provided)
dependenciesNoList of files this file imports/depends on (optional) - e.g., ["src/utils.ts", "src/types.ts"]
project_nameNoProject name to look up (alternative to project_id)
lines_of_codeNoApproximate line count (optional, for tracking growth)
workspace_pathNoWorkspace directory path (alternative to project_id)
last_modified_byNoYour agent_id from register_agent() (optional)
Behavior3/5

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

No annotations, so the description carries the full burden. It discloses project resolution priority (project_id > workspace_path > project_name) and enumerates file types and complexity levels. However, it never states update semantics: whether it overwrites all fields, merges provided fields, or what happens when metadata already exists. This is a significant gap for an 'update' tool.

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 overly long (approximately 250 words) and repetitive. It re-lists schema values for file types and complexity levels, includes promotional filler like 'RECOMMENDED FOR' and 'This helps build a dependency graph', and the off-topic project lookup paragraph adds confusion rather than value.

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?

The description includes usage scenarios, project lookup priority, and value enums, which is helpful. However, it lacks critical behavioral details about the update operation itself, such as whether partial updates merge or replace existing metadata, and it does not mention any output or acknowledgment. Given the rich schema, it is functional but incomplete.

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 100%, and each parameter already has a clear description. The description adds value by clarifying project identifier priority and by enumerating file type/complexity values, but these are also present in the schema. Baseline 3 is appropriate since the schema does the heavy lifting.

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 opens with 'Track important file metadata' but then shifts to 'This tool provides flexible project lookup' and discusses identifier resolution priority, which is more appropriate for a project lookup tool. The verb 'track' is ambiguous compared to the tool name's 'update', though the WHEN TO USE section clarifies it updates file metadata by listing scenarios like 'update complexity assessments'.

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?

Provides an explicit WHEN TO USE section with five concrete scenarios (after creating new files, understanding dependencies, updating complexity, organizing modules, refactoring). It does not name alternatives or exclusions, but the scenarios are clear enough to guide an agent. The RECOMMENDED FOR section adds further targeting.

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/siddiquesahabaj/CoordMCP'

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