Skip to main content
Glama
Sign In
wealthi-coach-mcp-server

wealthi-coach-mcp-server

Official
by wealthi-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Student Progress

get_student_progress
Read-onlyIdempotent

Retrieve a student's current XP, level, streak status, and points balance to monitor learning progress and engagement.

Instructions

Retrieve a student's current XP, level, streak, and points balance.

Reads from Firestore (users/{studentId}), which is the system of record for gamification/progress data. Does NOT include quiz-level detail — use get_assessment_results for that.

Args:

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

Returns: JSON object with schema: { "studentId": string, "xp": number, "level": number, "streakCount": number, "streakStatus": "active" | "at_risk" | "broken", "pointsBalance": number }

Error Handling:

  • Returns "Student not found" if no Firestore user document exists for student_id.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "student_id": "<student_id>"
    },
    "name": "get_student_progress"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive. The description adds valuable behavioral context: reads from Firestore, lists exact fields returned, specifies error handling ('Student not found'). This supplements the annotations well.

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

Conciseness4/5

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

The description is efficiently structured with sections for Args, Returns, and Error Handling. It front-loads the main purpose. Slightly verbose with the full return schema, but overall concise.

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 no output schema, the description provides a complete return type spec. It includes error handling and data source. Input schema is fully described. The tool is simple (1 param), and the description covers all necessary information.

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?

Schema description coverage is 100%, providing a detailed description of student_id. The description's Args section repeats a truncated version of the schema description, adding no new meaning. 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 states a specific verb and resource: 'Retrieve a student's current XP, level, streak, and points balance.' It explicitly distinguishes from a sibling tool: 'Does NOT include quiz-level detail — use get_assessment_results for that.'

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 provides clear context: it reads from Firestore and is for gamification/progress data. It explicitly directs to an alternative for quiz detail. However, no explicit when-not-to-use beyond quiz-level.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools