Skip to main content
Glama
wealthi-ai

wealthi-coach-mcp-server

Official
by wealthi-ai

Get Curriculum Progress

get_curriculum_progress
Read-onlyIdempotent

Check a student's progress across nine financial literacy topics by evaluating quiz attempt scores; returns completion status and module counts per topic.

Instructions

Retrieve a student's completion status across Wealthi's financial literacy topics (saving, budgeting, tradeoffs, delayed gratification, goal setting, decision making, financial confidence, future thinking, credit basics).

Derives completion from passing quiz attempts (score >= 70) grouped by topic and module, mapped against the same topic taxonomy used by Coach's content library (coachContent.ts) — so results align with what's shown in-app.

Args:

  • student_id (string): The student's unique identifier.

Returns: JSON object with schema: { "studentId": string, "topics": [ { "topicId": string, "topicLabel": string, "status": "not_started" | "in_progress" | "completed", "completedModules": number, "totalModules": number } ] }

Error Handling:

  • Always returns all 9 topics, even if the student hasn't started any (status will be "not_started" with completedModules: 0).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
student_idYesThe student's unique identifier (Firebase Auth UID / Supabase user_id — these are the same value across both systems).
Behavior5/5

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

The description adds substantial behavioral context beyond annotations: it explains the derivation logic (passing quiz scores >=70), grouping by topic/module, and guarantees it always returns all 9 topics even if unstarted. This complements the readOnlyHint and idempotentHint annotations without contradiction.

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 concise and well-structured: it opens with a clear purpose, then explains derivation, parameters, return schema, and error handling. Every sentence adds value, and the length is appropriate for the tool's complexity.

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

Completeness5/5

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

Despite having no output schema, the description provides a complete return schema and explains guaranteed behavior (all topics returned). With good annotations and a simple parameter, the description fully enables correct agent invocation without gaps.

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 single parameter `student_id` is well-documented in the schema (100% coverage) with a detailed description of its format (Firebase Auth UID / Supabase user_id). The description's Args section merely repeats this, adding no new meaning, so a baseline score of 3 is appropriate.

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 retrieves completion status across specific financial literacy topics, using a specific verb ('Retrieve') and resource ('student's completion status'). It implicitly distinguishes from siblings like `get_assessment_results` and `get_student_progress` by focusing on topic-level completion derived from quiz attempts.

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 explicit guidance on when to use this tool versus alternatives like `get_student_progress` or `get_assessment_results`. The description does not provide when-to-use or when-not-to-use context, leaving the agent to infer usage from purpose 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/wealthi-ai/wealthi-coach-mcp-server'

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