local-study-app
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_decksD | Local study app tool |
| get_deckC | Local study app tool |
| create_deckD | Local study app tool |
| update_deckD | Local study app tool |
| delete_deckD | Local study app tool |
| duplicate_deckD | Local study app tool |
| list_cardsD | Local study app tool |
| create_flashcardC | Local study app tool |
| delete_flashcardD | Local study app tool |
| generate_quiz_from_deckD | Local study app tool |
| record_card_reviewD | Local study app tool |
| get_due_cardsD | Local study app tool |
| get_study_progressD | Local study app tool |
| export_deckC | Local study app tool |
| import_deckC | Local study app tool |
| start_study_appD | Local study app tool |
| open_study_appD | Local study app tool |
| get_study_app_statusD | Local study app tool |
| stop_study_appC | Local study app tool |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 19 tools
Most tools have distinct purposes, but 'start_study_app' and 'open_study_app' may be ambiguous. Overall, the set is clear.
All tools use consistent snake_case with a verb_noun pattern, making naming predictable.
19 tools is slightly above typical range but justified by the app's scope including CRUD, study features, and app management.
Missing update_flashcard and get_flashcard, which are standard operations. This gap could cause agent failures when needing to update a specific flashcard.