Skip to main content
Glama

get_file_changelog

Retrieve changelog entries for a specific file to track modifications and maintain project awareness during coding sessions.

Instructions

Get changelog entries for a specific file

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filePathYesPath to the file

Implementation Reference

  • src/index.ts:703-712 (registration)
    Tool registration including name, description, and input schema for get_file_changelog
      name: 'get_file_changelog',
      description: 'Get changelog entries for a specific file',
      inputSchema: {
        type: 'object',
        properties: {
          filePath: { type: 'string', description: 'Path to the file' }
        },
        required: ['filePath']
      }
    },
  • Tool handler that extracts filePath argument and delegates to ChangelogManager.getChangelogForFile, returning JSON stringified result
    case 'get_file_changelog': {
      const filePath = args.filePath as string;
      const fileChangelog = await this.changelogManager.getChangelogForFile(filePath);
      return { content: [{ type: 'text', text: JSON.stringify(fileChangelog, null, 2) }] };
    }
  • Core helper method that loads full changelog, computes relative file path, and filters entries where the file appears in filesChanged array
    async getChangelogForFile(filePath: string): Promise<ChangelogEntry[]> {
      const changelog = await this.getChangelog();
      const relativePath = path.relative(this.projectRoot, filePath);
      
      return changelog.filter(entry => 
        entry.filesChanged.some(file => file === relativePath)
      );
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Get' implies a read operation, it doesn't specify whether this requires authentication, what format the changelog entries return in, whether there are rate limits, or if there are any side effects. The description is minimal and leaves critical behavioral questions unanswered.

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 a single, efficient sentence that gets straight to the point with zero wasted words. It's appropriately sized for a simple retrieval tool and front-loads the essential information without unnecessary elaboration.

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

Completeness2/5

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

For a tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what 'changelog entries' consist of, their format, whether this includes all history or recent changes only, or how the information might differ from what sibling tools provide. The minimal description leaves too many contextual gaps.

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 description coverage is 100%, with the single parameter 'filePath' clearly documented in the schema. The description doesn't add any additional parameter semantics beyond what the schema already provides, such as path format requirements or examples. The baseline of 3 is appropriate when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Get changelog entries') and target resource ('for a specific file'), making the purpose immediately understandable. However, it doesn't distinguish this tool from potential sibling tools like 'get_recent_changes' or 'parse_file_metadata', which might have overlapping functionality.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. With sibling tools like 'get_recent_changes' and 'parse_file_metadata' that might retrieve similar information, there's no indication of when this specific changelog retrieval is appropriate versus other change-tracking methods.

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/keleshteri/mcp-memory'

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