Skip to main content
Glama
Connectry-io

Connectry Architect Cert

Official

reset_progress

Permanently delete all study progress, including answers, mastery data, and review schedules. This action cannot be undone.

Instructions

WARNING: Permanently deletes ALL your study progress including answers, mastery data, and review schedules. This cannot be undone.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmedYesMust be true to confirm the reset

Implementation Reference

  • The main handler function for the reset_progress tool. Deletes all user progress data (answers, domain_mastery, review_schedule, session_state, study_sessions, handout_views, exam_attempts) across 7 tables, gated by a boolean 'confirmed' parameter.
    export function registerResetProgress(server: McpServer, db: Database.Database, userConfig: UserConfig): void {
      server.tool(
        'reset_progress',
        'WARNING: Permanently deletes ALL your study progress including answers, mastery data, and review schedules. This cannot be undone.',
        { confirmed: z.boolean().describe('Must be true to confirm the reset') },
        async ({ confirmed }) => {
          if (!confirmed) {
            return { content: [{ type: 'text' as const, text: 'Reset cancelled. Your progress is safe.' }] };
          }
          const userId = userConfig.userId;
          db.prepare('DELETE FROM answers WHERE userId = ?').run(userId);
          db.prepare('DELETE FROM domain_mastery WHERE userId = ?').run(userId);
          db.prepare('DELETE FROM review_schedule WHERE userId = ?').run(userId);
          db.prepare('DELETE FROM session_state WHERE userId = ?').run(userId);
          db.prepare('DELETE FROM study_sessions WHERE userId = ?').run(userId);
          db.prepare('DELETE FROM handout_views WHERE userId = ?').run(userId);
          db.prepare('DELETE FROM exam_attempts WHERE userId = ?').run(userId);
    
          return { content: [{ type: 'text' as const, text: 'All progress has been reset, including exam history. You can start fresh with start_assessment.' }] };
        }
      );
    }
  • Input schema for reset_progress: requires a boolean 'confirmed' parameter that must be true to proceed with the reset, with Zod validation.
    { confirmed: z.boolean().describe('Must be true to confirm the reset') },
  • Import of registerResetProgress from the reset-progress module.
    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);
      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);
    }
  • Registration call: registerResetProgress is invoked with server, db, and userConfig inside the registerTools function.
      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);
    }
Behavior4/5

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

With no annotations, the description fully discloses the destructive behavior: 'permanently deletes', 'cannot be undone', and lists what is deleted. This goes beyond the input schema, which only has a confirmation parameter.

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 one impactful sentence with a warning prefix. No extraneous words; front-loaded with critical information.

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 destructive action with one parameter, the description explains the consequence and confirmation requirement. No output schema exists, so return values are not needed. Minor improvement could mention what happens after reset, but it's adequate.

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 schema already documents the 'confirmed' parameter well (must be true to confirm). The tool description adds context about the consequence but does not add new parameter-specific meaning. With 100% schema coverage, baseline is 3.

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 deletes all study progress permanently. It uses strong verbs ('deletes') and specifies the resources (answers, mastery data, review schedules). This distinguishes it from sibling tools like get_progress or get_weak_areas.

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 does not provide explicit guidance on when to use this tool versus alternatives. It lacks conditions or examples of appropriate use cases. A warning is given but no when-not-to-use or alternative suggestions.

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