Skip to main content
Glama
Connectry-io

Connectry Architect Cert

Official

get_weak_areas

Find which task statements have accuracy below 70% to prioritize your study on weak areas.

Instructions

Identify your weakest task statements based on accuracy below 70%. Focus your study on these areas.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main tool handler that registers 'get_weak_areas' with the MCP server. It calls getWeakAreas from the database, formats the results with domain/statement names from the curriculum, and returns a formatted text response. If no weak areas exist, it returns a message saying so.
    export function registerGetWeakAreas(server: McpServer, db: Database.Database, userConfig: UserConfig): void {
      server.tool(
        'get_weak_areas',
        'Identify your weakest task statements based on accuracy below 70%. Focus your study on these areas.',
        {},
        async () => {
          const userId = userConfig.userId;
          ensureUser(db, userId);
          const curriculum = loadCurriculum();
          const weakAreas = getWeakAreas(db, userId);
    
          if (weakAreas.length === 0) {
            return {
              content: [{ type: 'text' as const, text: 'No weak areas identified yet. Complete some questions first or all areas are above 70%!' }],
            };
          }
    
          const lines = ['═══ WEAK AREAS ═══', ''];
          for (const area of weakAreas) {
            const domain = curriculum.domains.find(d => d.id === area.domainId);
            const ts = domain?.taskStatements.find(t => t.id === area.taskStatement);
            lines.push(`  ${area.taskStatement}: ${ts?.title ?? 'Unknown'}`);
            lines.push(`    Accuracy: ${area.accuracyPercent}% (${area.correctAttempts}/${area.totalAttempts})`);
            lines.push(`    Mastery: ${area.masteryLevel}`);
            lines.push('');
          }
          return { content: [{ type: 'text' as const, text: lines.join('\n') }] };
        }
      );
    }
  • Database helper function that queries domain_mastery for rows with accuracyPercent below a threshold (default 70) and totalAttempts > 0, ordered ascending by accuracy.
    export function getWeakAreas(db: Database.Database, userId: string, threshold: number = 70): readonly DomainMastery[] {
      return db.prepare('SELECT * FROM domain_mastery WHERE userId = ? AND accuracyPercent < ? AND totalAttempts > 0 ORDER BY accuracyPercent ASC').all(userId, threshold) as DomainMastery[];
    }
  • Central registration point that calls registerGetWeakAreas(server, db, userConfig) at line 30 to wire up the tool.
    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);
    }
  • The tool has an empty schema object {} (no input parameters required), with the description: 'Identify your weakest task statements based on accuracy below 70%. Focus your study on these areas.'
    {},
Behavior3/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. It specifies the accuracy threshold (70%) but does not disclose whether the tool is read-only, requires auth, or any side effects. More detail would improve transparency.

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?

Two sentences with no wasted words. The description is front-loaded with the key purpose and a direct actionable suggestion. Every sentence earns its place.

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?

The description gives the tool's purpose and a threshold, but lacks output details (e.g., format, data structure). With no output schema, the agent is left guessing the return value, reducing completeness.

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 the description inherently adds no parameter info beyond the schema. Baseline 4 applies as per guidelines for 0-parameter tools.

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 states the tool identifies weakest task statements based on accuracy below 70%, providing a specific verb and resource. It is distinct from sibling tools like get_progress or get_dashboard, though it doesn't explicitly differentiate.

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?

The description implies usage for study focus but lacks explicit when-to-use or when-not-to-use guidance. No alternatives are mentioned, leaving the agent to infer context.

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