Skip to main content
Glama

get_all_changes

Retrieve all changes from the change ledger, with optional filtering by ISO timestamp for targeted codebase history.

Instructions

Get all changes in the ledger, optionally filtered by ISO timestamp.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sinceNo

Implementation Reference

  • Core handler for get_all_changes: reads full ledger, optionally filters by ISO timestamp 'since', returns entries with branch and short SHA context.
    async function getAllChanges(since?: string): Promise<LedgerQueryResult> {
      const [entries, context] = await Promise.all([
        fs.readLedger(ledgerPath),
        git.getBranchContext(repoDir),
      ]);
    
      const filtered = since
        ? entries.filter((e) => e.timestamp >= since)
        : entries;
    
      return {
        entries: filtered,
        branch: context.branch,
        sha: context.shortSha,
      };
    }
  • Zod schema for get_all_changes inputs: optional 'since' string parameter.
    export const GetAllChangesSchema = z.object({
      since: z.string().optional(),
    });
  • Registration of the 'get_all_changes' MCP tool on the server, wiring schema and calling manager.getAllChanges.
    server.tool('get_all_changes', 'Get all changes in the ledger, optionally filtered by ISO timestamp.', GetAllChangesSchema.shape, async (args) => {
      const result = await manager.getAllChanges(args.since);
      return {
        content: [{ type: 'text' as const, text: JSON.stringify(result, null, 2) }],
      };
    });
  • LedgerManager interface declaring getAllChanges(since?: string).
    export interface LedgerManager {
      logChange(input: LogChangeInput): Promise<LedgerEntry>;
      getSessionChanges(sessionId: string): Promise<LedgerQueryResult>;
      getFileLedger(filePath: string): Promise<LedgerQueryResult>;
      getAllChanges(since?: string): Promise<LedgerQueryResult>;
    }
Behavior2/5

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

No annotations are provided, and the description fails to disclose behavioral traits such as read-only nature, pagination, or performance implications. It only states the basic function.

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 extremely concise with a single sentence that front-loads the key information. No redundant words.

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 output schema and minimal description, the tool lacks completeness. It does not explain what constitutes a change, return format, or pagination, making it insufficient for agents.

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?

The description adds meaning to the 'since' parameter by stating it expects an ISO timestamp, but it does not specify format or provide examples. Schema coverage is 0%, so the description partially compensates.

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 it retrieves all changes in the ledger and optionally filters by ISO timestamp, which is specific and distinguishes it from sibling tools like get_changed_files. However, it does not define 'changes' further.

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 usage guidance is provided; there is no mention of when to use this tool versus alternatives like get_changed_files or get_session_changes. The description is purely functional.

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/2loch-ness6/mempalace-mcp-dev'

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