Skip to main content
Glama
Connectry-io

Connectry Architect Cert

Official

capstone_build_status

Monitor your guided capstone build progress including current step, criteria coverage, and quiz performance.

Instructions

Check your guided capstone build progress — current step, criteria coverage, and quiz performance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler registration for the 'capstone_build_status' tool. Calls server.tool() with name 'capstone_build_status'. Checks for an active build, handles 'shaping' vs 'building' status, and formats the status report with steps, criteria coverage, and quiz performance.
    export function registerCapstoneBuildStatus(server: McpServer, db: Database.Database, userConfig: UserConfig): void {
      server.tool(
        'capstone_build_status',
        'Check your guided capstone build progress \u2014 current step, criteria coverage, and quiz performance.',
        {},
        async () => {
          const userId = userConfig.userId;
          const build = getActiveBuild(db, userId);
    
          if (!build) {
            return {
              content: [{
                type: 'text' as const,
                text: 'No active capstone build found. Use start_capstone_build to begin a guided build.',
              }],
            };
          }
    
          if (build.status === 'shaping') {
            const lines = [
              '=== CAPSTONE BUILD STATUS ===',
              '',
              `Theme: ${build.theme}`,
              'Status: Shaping',
              '',
              'Your theme is being shaped. You can:',
              '  - Confirm it to start building',
              '  - Refine it with a new description',
            ];
            return {
              content: [{ type: 'text' as const, text: lines.join('\n') }],
            };
          }
    
          // Status is 'building'
          const steps = getBuildSteps(db, build.id);
          const quizQuestionIds = collectQuizQuestionIds(steps);
          const quizPerformance = getQuizPerformance(db, userId, quizQuestionIds);
    
          const text = formatBuildingStatus(build.theme, build.currentStep, steps, quizPerformance);
    
          return {
            content: [{ type: 'text' as const, text }],
          };
        }
      );
    }
  • QuizStats interface used to structure quiz performance data (domainId, total, correct).
    interface QuizStats {
      readonly domainId: number;
      readonly total: number;
      readonly correct: number;
    }
  • Helper function collectQuizQuestionIds - extracts quiz question IDs from build steps by parsing JSON.
    function collectQuizQuestionIds(steps: readonly CapstoneBuildStep[]): readonly string[] {
      return steps.flatMap(step => {
        if (!step.quizQuestionIds) return [];
        const parsed = JSON.parse(step.quizQuestionIds) as readonly string[];
        return [...parsed];
      });
    }
  • Helper function getQuizPerformance - queries the answers table to get per-domain quiz performance stats.
    function getQuizPerformance(db: Database.Database, userId: string, questionIds: readonly string[]): readonly QuizStats[] {
      if (questionIds.length === 0) return [];
    
      const placeholders = questionIds.map(() => '?').join(', ');
      const rows = db.prepare(
        `SELECT domainId, COUNT(*) as total, SUM(CASE WHEN isCorrect THEN 1 ELSE 0 END) as correct
         FROM answers
         WHERE userId = ? AND questionId IN (${placeholders})
         GROUP BY domainId
         ORDER BY domainId ASC`
      ).all(userId, ...questionIds) as Array<{ domainId: number; total: number; correct: number }>;
    
      return rows.map(r => ({
        domainId: r.domainId,
        total: r.total,
        correct: r.correct ?? 0,
      }));
    }
  • Import of registerCapstoneBuildStatus in the central tools registration file.
    import { registerCapstoneBuildStatus } from './capstone-build-status.js';
    import { registerDashboard } from './dashboard.js';
    
    export function registerTools(server: McpServer, db: Database.Database, userConfig: UserConfig): void {
      registerSubmitAnswer(server, db, userConfig);
      registerGetProgress(server, db, userConfig);
      registerGetCurriculum(server, db, userConfig);
      registerGetSectionDetails(server, db, userConfig);
      registerGetPracticeQuestion(server, db, userConfig);
      registerStartAssessment(server, db, userConfig);
      registerGetWeakAreas(server, db, userConfig);
      registerGetStudyPlan(server, db, userConfig);
      registerScaffoldProject(server, db, userConfig);
      registerResetProgress(server, db, userConfig);
      registerStartPracticeExam(server, db, userConfig);
      registerSubmitExamAnswer(server, db, userConfig);
      registerGetExamHistory(server, db, userConfig);
      registerFollowUp(server, db, userConfig);
      registerStartCapstoneBuild(server, db, userConfig);
      registerCapstoneBuildStep(server, db, userConfig);
      registerCapstoneBuildStatus(server, db, userConfig);
      registerDashboard(server, db, userConfig);
    }
Behavior3/5

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

No annotations are provided, and the description does not disclose behavioral traits beyond the return values. It does not mention whether it is read-only, requires an active project, or has side effects. However, the tool is inherently a read operation.

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, well-structured sentence that front-loads the core purpose and specific outputs. Every word adds value with no redundancy.

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

Completeness4/5

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

For a parameterless tool with no annotations or output schema, the description adequately covers what the tool does and what it returns. Minor gap: does not specify prerequisites like having an active capstone build.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are no parameters in the schema, so the description does not need to explain them. With 100% schema coverage (no params), the description adds no param details, which is acceptable per guidelines.

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 clearly states the tool checks 'guided capstone build progress' and lists specific return elements (current step, criteria coverage, quiz performance). It distinguishes itself from siblings like 'capstone_build_step' and 'start_capstone_build' by focusing on overall status.

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

Usage Guidelines3/5

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

No explicit guidance on when to use this tool versus alternatives such as 'capstone_build_step' or 'get_progress'. The context implies it is for holistic status, but no when-not-to-use or alternative comparison is provided.

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/Connectry-io/connectrylab-architect-cert-mcp'

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