Skip to main content
Glama

elenchus_get_project_history

Retrieve verification history for a project to access past sessions and baselines, enabling review of previous analysis results without starting from scratch.

Instructions

Get verification history for a project including past sessions and baselines.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workingDirYesWorking directory for the project

Implementation Reference

  • The handler function that executes the 'elenchus_get_project_history' tool logic. It calls getProjectIndex to load the project index from disk and returns the history (past sessions) and last verified session info.
    export async function getProjectHistoryTool(
      args: z.infer<typeof GetProjectHistorySchema>
    ): Promise<{
      hasHistory: boolean;
      projectPath: string;
      history?: Array<{
        sessionId: string;
        timestamp: string;
        verdict: string;
        target: string;
      }>;
      lastVerified?: {
        sessionId: string;
        timestamp: string;
        gitCommit?: string;
      };
    }> {
      const index = await getProjectIndex(args.workingDir);
    
      if (!index) {
        return {
          hasHistory: false,
          projectPath: args.workingDir
        };
      }
    
      return {
        hasHistory: true,
        projectPath: args.workingDir,
        history: index.history,
        lastVerified: index.lastVerifiedSession ? {
          sessionId: index.lastVerifiedSession,
          timestamp: index.lastVerifiedTimestamp || '',
          gitCommit: index.lastVerifiedCommit
        } : undefined
      };
    }
  • Zod schema for input validation of the 'elenchus_get_project_history' tool. Takes a single required field: workingDir (string).
    export const GetProjectHistorySchema = z.object({
      workingDir: z.string().describe('Working directory for the project')
    });
  • The tool registration entry that maps 'elenchus_get_project_history' to its schema and handler. This is part of the diffTools object exported from diff-tools.ts.
      elenchus_get_project_history: {
        description: 'Get verification history for a project including past sessions and baselines.',
        schema: GetProjectHistorySchema,
        handler: getProjectHistoryTool
      }
    };
  • The final tool composition that spreads diffTools (including elenchus_get_project_history) into the unified tools export.
    export const tools = {
      ...sessionLifecycleTools,
      ...issueManagementTools,
      ...mediatorTools,
      ...roleTools,
      ...reverifyTools,
      ...diffTools,
      ...cacheTools,
      ...pipelineTools,
      ...safeguardsTools,
      ...optimizationTools,
      ...dynamicRoleTools,
      ...llmEvalTools,
    };
  • Helper function getProjectIndex that reads the project index from disk (index.json). Used by the handler to retrieve history data.
    export async function getProjectIndex(
      projectPath: string
    ): Promise<ProjectIndex | null> {
      try {
        const indexPath = path.join(getProjectDir(projectPath), 'index.json');
        const content = await fs.readFile(indexPath, 'utf-8');
        return JSON.parse(content);
      } catch {
        return null;
      }
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states what the tool returns (history) but does not disclose whether it is read-only, any side effects, output format, or limitations.

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 concise sentence that directly states purpose without extraneous 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 many siblings, the description lacks details about the return structure, pagination, or what constitutes history. It is insufficient for an AI agent to understand all usage contexts.

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% with one parameter described as 'Working directory for the project'. The description adds no extra meaning beyond the schema, meeting baseline but not exceeding it.

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?

The description uses a specific verb 'Get' and identifies the resource 'verification history for a project', clearly distinguishing it from siblings like elenchus_get_context or elenchus_get_diff_summary.

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 on when to use this tool versus alternatives. Siblings exist for similar purposes (e.g., elenchus_get_context), but the description does not differentiate usage context or provide exclusions.

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/jhlee0409/elenchus-mcp'

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