A FastAPI application that allows students to view and sign up for extracurricular activities at Mergington High School
This FastAPI server exposes 3 tools with basic schemas and descriptions, but falls short of production quality across multiple dimensions. All three tools have descriptions (good), but they are terse and lack LLM-optimized guidance. Parameter descriptions are minimal or absent. Output schemas are not formally documented. Error handling provides HTTP status codes but no actionable recovery guidance. The server is designed as a traditional web API, not as an MCP tool provider, and does not implement MCP transport or protocol features.
Retrieve all extracurricular activities with their details including description, schedule, max participants, and current participants
Sign up a student for an activity
Unregister a student from an activity
Missing output schema documentation. None of the three tools formally document their return types or fields. LLMs cannot plan downstream operations or extract the right data without knowing what fields to expect.
Terse parameter descriptions lacking LLM guidance. 'activity_name' and 'email' parameters in signup_for_activity and unregister_from_activity have minimal descriptions ('The name of the activity to sign up for', 'The student's email address'). These do not explain format expectations, valid values, or constraints. LLMs need explicit guidance on what constitutes valid input.
Error responses lack recovery guidance. The FastAPI handlers return HTTPException with generic messages ('Activity not found', 'Student is already signed up') but do not guide the LLM on what to do next. For example, when an activity is not found, the error should suggest calling get_activities() first or provide a list of available activities.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 43 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 25 | - | v1 |
Tool descriptions are under 100 characters and lack context. 'Retrieve all extracurricular activities...' (65 chars) is functional but does not explain WHEN to use this tool vs others, whether it supports filtering, or how it integrates with signup tools. Descriptions should be 50-200 chars with explicit dependency hints.
get_activities has no input parameters but its description does not clarify whether it returns all activities or supports filtering. A description like 'Retrieve all activities (cannot filter by schedule or availability)' would prevent LLMs from requesting non-existent filters.
No pagination or result limiting mechanism. get_activities returns the entire in-memory dictionary. If this grows to thousands of activities, returning all of them wastes tokens and risks context window exhaustion. Should return paginated results with limit/offset parameters and a total count.
Signup and unregister operations lack idempotency or confirmation. If signup_for_activity fails midway and the LLM retries, it may fail with 'Student is already signed up' instead of succeeding. Idempotent operations or a confirmation step could prevent this. Irreversible state changes (signup/unregister) benefit from dry-run or confirmation patterns.
No capacity validation in signup_for_activity. The tool does not check whether the activity has reached max_participants before adding the student. An LLM could fail silently (or add beyond capacity) without being told that the activity is full.