Skip to main content
Glama
core3-coder

Context Continuation MCP Server

by core3-coder

context_get_project_summary

Generate a detailed project summary by analyzing the specified project directory, enabling efficient context management and AI development insights.

Instructions

Get a comprehensive project summary

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectPathYesPath to project directory

Implementation Reference

  • The getProjectSummary method implements the core logic for the 'context_get_project_summary' tool by computing project statistics from session files, milestones, and configuration in the .context directory.
    async getProjectSummary(projectPath: string): Promise<ProjectSummary> {
      const contextDir = path.join(projectPath, '.context');
      const config = await this.loadConfig(projectPath);
      
      // Get all sessions
      const sessionsDir = path.join(contextDir, 'sessions');
      const sessions = await this.getAllSessions(sessionsDir);
      
      // Calculate stats
      const totalTokens = sessions.reduce((acc, s) => acc + s.tokenCount, 0);
      const lastActivity = sessions.length > 0 
        ? new Date(Math.max(...sessions.map(s => s.startTime.getTime())))
        : new Date();
    
      // Get milestones
      const milestones = await this.getMilestones(projectPath);
    
      return {
        name: config.projectName || path.basename(projectPath),
        path: projectPath,
        totalSessions: sessions.length,
        totalTokens,
        lastActivity,
        currentPhase: await this.getCurrentPhase(projectPath),
        keyMilestones: milestones.slice(0, 5), // Most recent 5
      };
    }
  • TypeScript interface defining the structure of the project summary returned by the tool.
    export interface ProjectSummary {
      name: string;
      path: string;
      totalSessions: number;
      totalTokens: number;
      lastActivity: Date;
      currentPhase?: string;
      keyMilestones: Milestone[];
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'comprehensive' but doesn't specify what that includes (e.g., timeline, resources, risks), whether it's read-only, requires permissions, or has side effects. For a tool with no annotation coverage, this leaves significant gaps in understanding its behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with no wasted words. It's front-loaded with the core action ('Get a comprehensive project summary'), making it easy to parse. However, it could be more structured by explicitly stating the tool's scope or limitations.

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, no output schema, and a single parameter with good schema coverage, the description is incomplete. It doesn't explain what the summary includes, how it's formatted, or potential errors. For a tool that likely returns complex project data, more context is needed to guide effective use.

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 input schema has 100% description coverage, with 'projectPath' clearly documented as 'Path to project directory'. The description adds no additional meaning beyond this, such as format examples or constraints. With high schema coverage, the baseline score of 3 is appropriate as the schema handles the parameter documentation adequately.

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 a comprehensive project summary' states a clear verb ('Get') and resource ('project summary'), but it's somewhat vague about what constitutes 'comprehensive' and doesn't distinguish this tool from potential sibling tools like 'context_get_status' that might also retrieve project information. It's functional but lacks specificity.

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 siblings like 'context_get_status' available, there's no indication of whether this tool is for high-level overviews, detailed reports, or specific contexts. Usage is implied only by the name, not explained.

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

Related 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/core3-coder/context-continue-mcp'

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