Skip to main content
Glama

get_recent_changes

Retrieve recent changelog entries from the MCP Memory Server to track coding session modifications and project updates.

Instructions

Get recent changelog entries

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoNumber of days to look back (default: 7)

Implementation Reference

  • The core handler function implementing the tool logic: fetches full changelog and filters entries from the last N days (default: 7).
    async getRecentChanges(days: number = 7): Promise<ChangelogEntry[]> {
      const changelog = await this.getChangelog();
      const cutoffDate = new Date();
      cutoffDate.setDate(cutoffDate.getDate() - days);
      
      return changelog.filter(entry => 
        new Date(entry.date) > cutoffDate
      );
    }
  • src/index.ts:713-722 (registration)
    Tool registration in the MCP server's listTools handler, defining name, description, and input schema.
    {
      name: 'get_recent_changes',
      description: 'Get recent changelog entries',
      inputSchema: {
        type: 'object',
        properties: {
          days: { type: 'number', description: 'Number of days to look back (default: 7)' }
        }
      }
    },
  • MCP server tool dispatch handler: parses arguments, calls ChangelogManager.getRecentChanges, and formats response.
    case 'get_recent_changes': {
      const days = (args.days as number) || 7;
      const recentChanges = await this.changelogManager.getRecentChanges(days);
      return { content: [{ type: 'text', text: JSON.stringify(recentChanges, null, 2) }] };
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It doesn't disclose whether this is a read-only operation, how results are returned (e.g., pagination, format), rate limits, or authentication needs. 'Get' implies a read, but lacks confirmation of safety or other traits.

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 with zero waste. It's front-loaded with the core purpose and appropriately sized for a simple tool, making it easy for an agent to parse quickly.

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?

Given no annotations and no output schema, the description is incomplete for a tool that likely returns data. It doesn't explain what 'changelog entries' contain, how they're structured, or any limitations. For a data retrieval tool, more context on output behavior is needed beyond the minimal input parameter info.

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 'days' parameter fully documented in the schema. The description adds no additional parameter semantics beyond implying 'recent' relates to time, which aligns with the schema's 'days' parameter. 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 'Get recent changelog entries' clearly states the action (get) and resource (changelog entries), but it's vague about scope and doesn't distinguish from sibling tools like 'get_file_changelog' or 'add_changelog_entry'. It specifies 'recent' but doesn't clarify what that means compared to other changelog tools.

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?

No guidance is provided on when to use this tool versus alternatives like 'get_file_changelog' or 'add_changelog_entry'. The description implies it's for recent entries, but doesn't specify use cases, prerequisites, or exclusions, leaving the agent to guess based on tool names alone.

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