Skip to main content
Glama
Connectry-io

Connectry Architect Cert

Official

get_study_plan

Generate a personalized study plan from assessment results to target weak areas. Track progress with a dynamic checklist and select focus domains to filter practice questions.

Instructions

Get a personalized study plan based on your assessment results, weak areas, and learning path.

IMPORTANT — after showing the study plan, use AskUserQuestion with header "Focus" and multiSelect: true to let the user pick which domains they want to focus on. Options should be the 5 domains with their current mastery as descriptions. Then use their selection to filter get_practice_question calls.

Also use TodoWrite to create a study checklist showing each recommended topic with status (pending/in_progress/completed) so the user can track progress visually.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function that registers and implements the 'get_study_plan' MCP tool. It builds a personalized study plan by determining the next recommended domain, domain order, time estimate, overdue reviews, and mastery data using the user's learning path.
    export function registerGetStudyPlan(server: McpServer, db: Database.Database, userConfig: UserConfig): void {
      server.tool(
        'get_study_plan',
        `Get a personalized study plan based on your assessment results, weak areas, and learning path.
    
    IMPORTANT — after showing the study plan, use AskUserQuestion with header "Focus" and multiSelect: true to let the user pick which domains they want to focus on. Options should be the 5 domains with their current mastery as descriptions. Then use their selection to filter get_practice_question calls.
    
    Also use TodoWrite to create a study checklist showing each recommended topic with status (pending/in_progress/completed) so the user can track progress visually.`,
        {},
        async () => {
          const userId = userConfig.userId;
          ensureUser(db, userId);
          const user = getUser(db, userId);
          const curriculum = loadCurriculum();
          const mastery = getAllMastery(db, userId);
          const overdueReviews = getOverdueReviews(db, userId);
          const stats = getTotalStats(db, userId);
          const allQuestions = loadQuestions();
          const path = user?.learningPath ?? 'beginner-friendly';
    
          const masteryByDomain = new Map<number, typeof mastery>();
          for (const m of mastery) {
            const existing = masteryByDomain.get(m.domainId) ?? [];
            masteryByDomain.set(m.domainId, [...existing, m]);
          }
    
          const nextDomain = getNextRecommendedDomain(path as any, masteryByDomain);
          const domainOrder = getDomainOrder(path as any);
          const timeEstimate = estimateTimeRemaining(allQuestions.length, stats.total);
    
          const domain = curriculum.domains.find(d => d.id === nextDomain);
    
          const lines = [
            '═══ YOUR STUDY PLAN ═══',
            '',
            `Learning Path: ${path}`,
            `Estimated Time Remaining: ${timeEstimate}`,
            '',
            `Next Recommended Domain: D${nextDomain} — ${domain?.title ?? 'Unknown'}`,
            '',
            'Domain Study Order:',
            ...domainOrder.map((id, i) => {
              const d = curriculum.domains.find(x => x.id === id);
              return `  ${i + 1}. D${id}: ${d?.title ?? 'Unknown'}`;
            }),
            '',
            `Reviews Due: ${overdueReviews.length}`,
            overdueReviews.length > 0 ? 'Start with your overdue reviews before new material.' : '',
          ];
          return { content: [{ type: 'text' as const, text: lines.join('\n') }] };
        }
      );
    }
  • The description/schema for the get_study_plan tool. It has an empty params object ({}) and provides instructions about showing the study plan, using AskUserQuestion with multiSelect for focus areas, and using TodoWrite for tracking progress.
        `Get a personalized study plan based on your assessment results, weak areas, and learning path.
    
    IMPORTANT — after showing the study plan, use AskUserQuestion with header "Focus" and multiSelect: true to let the user pick which domains they want to focus on. Options should be the 5 domains with their current mastery as descriptions. Then use their selection to filter get_practice_question calls.
    
    Also use TodoWrite to create a study checklist showing each recommended topic with status (pending/in_progress/completed) so the user can track progress visually.`,
        {},
  • Where registerGetStudyPlan is called to register the tool with the MCP server.
    registerGetStudyPlan(server, db, userConfig);
  • Import of registerGetStudyPlan from the get-study-plan module.
    import { registerGetStudyPlan } from './get-study-plan.js';
  • Helper function estimateTimeRemaining that calculates the time estimate shown in the study plan.
    export function estimateTimeRemaining(totalQuestions: number, answeredQuestions: number, avgSecondsPerQuestion: number = 45): string {
      const remaining = totalQuestions - answeredQuestions;
      const totalMinutes = Math.round((remaining * avgSecondsPerQuestion) / 60);
      const hours = Math.floor(totalMinutes / 60);
      const minutes = totalMinutes % 60;
      if (hours === 0) return `${minutes} minutes`;
      return `${hours} hours ${minutes} minutes`;
    }
Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It only says the tool gets a plan but does not disclose behavioral traits such as side effects, required prior state (e.g., assessment completed), or whether it modifies data. The instructions about AskUserQuestion and TodoWrite are about the agent's actions, not the tool's behavior.

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

Conciseness2/5

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

The description is overly long and mixes the tool's purpose with multi-step agent instructions (AskUserQuestion and TodoWrite). The first sentence is concise, but the rest adds verbosity that could be separated. This reduces clarity for tool selection.

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?

Given no parameters and no output schema, the description should at least describe what the study plan contains. It only says 'personalized' but does not detail the structure (e.g., list of topics, time estimates). The additional instructions compensate somewhat for missing output info, but the lack of output format is a gap.

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?

The input schema has zero parameters, so parameter semantics are not needed. The baseline for 0 parameters is 4, and the description adds no parameter information beyond what is already implied (no input required). No deduction needed.

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 'Get a personalized study plan based on your assessment results, weak areas, and learning path.' This provides a specific verb ('Get'), resource ('study plan'), and context, distinguishing it from siblings like get_curriculum or get_dashboard.

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

Usage Guidelines4/5

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

The description explicitly tells the agent what to do after invoking the tool: show the plan, then use AskUserQuestion to let the user pick domains, then filter practice questions. It provides a clear usage flow, though it does not explicitly mention when NOT to use this tool or alternative tools.

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