Skip to main content
Glama
Connectry-io

Connectry Architect Cert

Official

get_progress

Retrieve your certification study progress overview, including mastery levels, accuracy, and review status.

Instructions

Get your certification study progress overview including mastery levels, accuracy, and review status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registers the 'get_progress' MCP tool. It retrieves user progress: loads curriculum, calculates domain-level accuracy and mastered counts, computes overall stats (questions answered + accuracy), and counts overdue reviews. Returns a formatted text summary.
    export function registerGetProgress(server: McpServer, db: Database.Database, userConfig: UserConfig): void {
      server.tool(
        'get_progress',
        'Get your certification study progress overview including mastery levels, accuracy, and review status.',
        {},
        async () => {
          const userId = userConfig.userId;
          ensureUser(db, userId);
          const curriculum = loadCurriculum();
          const mastery = getAllMastery(db, userId);
          const stats = getTotalStats(db, userId);
          const overdueReviews = getOverdueReviews(db, userId);
    
          const domainProgress = curriculum.domains.map(d => {
            const domainMastery = mastery.filter(m => m.domainId === d.id);
            const avgAccuracy = domainMastery.length > 0
              ? Math.round(domainMastery.reduce((sum, m) => sum + m.accuracyPercent, 0) / domainMastery.length)
              : 0;
            const masteredCount = domainMastery.filter(m => m.masteryLevel === 'mastered').length;
            return `  D${d.id}: ${d.title} — ${avgAccuracy}% accuracy, ${masteredCount}/${d.taskStatements.length} mastered`;
          });
    
          const overallAccuracy = stats.total > 0 ? Math.round((stats.correct / stats.total) * 100) : 0;
    
          const text = [
            '═══ CERTIFICATION STUDY PROGRESS ═══',
            '',
            `Questions Answered: ${stats.total}`,
            `Overall Accuracy: ${overallAccuracy}%`,
            `Reviews Due: ${overdueReviews.length}`,
            '',
            'Domain Progress:',
            ...domainProgress,
          ].join('\n');
    
          return { content: [{ type: 'text' as const, text }] };
        }
      );
    }
  • Registration point: imports and calls registerGetProgress as part of the central registerTools function.
    import { registerGetProgress } from './get-progress.js';
    import { registerGetCurriculum } from './get-curriculum.js';
    import { registerGetSectionDetails } from './get-section-details.js';
    import { registerGetPracticeQuestion } from './get-practice-question.js';
    import { registerStartAssessment } from './start-assessment.js';
    import { registerGetWeakAreas } from './get-weak-areas.js';
    import { registerGetStudyPlan } from './get-study-plan.js';
    import { registerScaffoldProject } from './scaffold-project.js';
    import { registerResetProgress } from './reset-progress.js';
    import { registerStartPracticeExam } from './start-practice-exam.js';
    import { registerSubmitExamAnswer } from './submit-exam-answer.js';
    import { registerGetExamHistory } from './get-exam-history.js';
    import { registerFollowUp } from './follow-up.js';
    import { registerStartCapstoneBuild } from './start-capstone-build.js';
    import { registerCapstoneBuildStep } from './capstone-build-step.js';
    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);
  • Queries all domain mastery records for a user, used to compute domain progress.
    export function getAllMastery(db: Database.Database, userId: string): readonly DomainMastery[] {
      return db.prepare('SELECT * FROM domain_mastery WHERE userId = ? ORDER BY domainId, taskStatement').all(userId) as DomainMastery[];
    }
  • Returns total and correct answer counts for a user, used to compute overall accuracy.
    export function getTotalStats(db: Database.Database, userId: string): { total: number; correct: number } {
      const row = db.prepare('SELECT COUNT(*) as total, SUM(CASE WHEN isCorrect THEN 1 ELSE 0 END) as correct FROM answers WHERE userId = ?').get(userId) as { total: number; correct: number };
      return { total: row.total, correct: row.correct ?? 0 };
    }
  • Returns overdue review entries for a user, used to show how many reviews are due.
    export function getOverdueReviews(db: Database.Database, userId: string): readonly ReviewScheduleEntry[] {
      return db.prepare('SELECT * FROM review_schedule WHERE userId = ? AND nextReviewAt <= CURRENT_TIMESTAMP ORDER BY nextReviewAt ASC').all(userId) as ReviewScheduleEntry[];
    }
Behavior2/5

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

With no annotations, the description carries the full burden. It indicates a read operation ('Get') but does not disclose data freshness, authentication requirements, or whether the progress is real-time. The description is too minimal to fully inform the agent about behavioral 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, front-loaded sentence with no extraneous information. Every word contributes to the purpose, making it efficient and easy to parse.

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

Completeness3/5

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

For a simple parameterless tool, the description covers the return themes but lacks output schema or details on structure. It does not mention whether results are aggregated or per-section, leaving some ambiguity. The description is adequate but not comprehensive.

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, so schema coverage is 100% (trivial). The description adds value by explaining what the tool returns, which is not evident from the empty schema. Baseline 4 for zero parameters is appropriate.

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 identifies the tool as retrieving a certification study progress overview with specifics on mastery levels, accuracy, and review status. It is clear, but does not explicitly distinguish itself from sibling tools like get_dashboard or get_study_plan, which may overlap.

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 is provided. It does not mention prerequisites, limitations, or exclusions, leaving the agent to infer context from the tool name 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/Connectry-io/connectrylab-architect-cert-mcp'

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