artsonia-mcp
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| artsonia_healthcheckA | Confirm credentials are configured, log in, fetch the dashboard, and report {authenticated, transport, student_count} with a plain-English hint distinguishing "no creds" vs "bad creds" vs "site error". Read-only. |
| artsonia_list_studentsA | List the student(s) on your Artsonia parent/fan account with their artist_id, name, school, grade, and artwork/fan counts. The artist_id is the selector used by the portfolio, comments, and fan tools. |
| artsonia_get_activityB | Return the notification/activity feed on the parent dashboard (e.g. new teacher feedback, fan-club prompts), with a count and the list of notices. |
| artsonia_get_portfolioA | List a student's artworks (artwork_id, is_private flag, thumbnail). Pass the artist_id from artsonia_list_students. Set include_details:true to also fetch each artwork's full detail (title, project, grade, views, …) in one call — this fetches a detail page per artwork (slower), so leave it off when the lean tiles are enough. |
| artsonia_get_artworkA | Get one artwork: title, artist screen-name, view count, project (assignment name), and the comments on it. Pass an artwork_id from a portfolio. |
| artsonia_list_commentsA | List the comments on a given artwork (author + text). Pass an artwork_id from a portfolio. |
| artsonia_get_fansA | List the fans (name + relationship) in a student's fan club. Pass the artist_id from artsonia_list_students. |
| artsonia_get_feedbackA | List the teacher feedback left on a student's artwork — each item's message, who posted it and when, the artwork it's about, and whether it's been marked as read. Pass the artist_id from artsonia_list_students. |
| artsonia_mark_feedback_readA | Mark the student's teacher feedback as read (this is a mark-ALL action — Artsonia has no per-item control). Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). |
| artsonia_get_awardsA | List a student's Artsonia awards/achievement badges — current-year badges (name, earned/not, criteria, progress) plus badges earned in prior years. Pass the artist_id from artsonia_list_students. |
| artsonia_get_profileA | Show your Artsonia parent/fan account profile: name, email, mobile, and current notification opt-in states (news / artist activity / promos). Read-only complement to artsonia_set_notifications. |
| artsonia_download_artworkA | Download full-resolution images of a student's artwork to a local folder, named from the artwork title/project/grade and time-stamped to the image's source date. Optionally filter by class/project (substring), grade, and/or keep only the most-recent N (the portfolio is reliably newest-first). Re-runs are idempotent (skip_existing). Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview (the resolved filenames with estimated bytes; nothing is written) and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). write_metadata:true also saves each artwork's comments + teacher feedback as a .json sidecar next to its image. embed_metadata:true embeds title/project/grade/date into each JPEG's EXIF/IPTC. path_template (e.g. "{grade}/{project}" or "{school_year}") organizes downloads into subfolders for multi-year archives. Note: descriptive filenames need each artwork's detail page (slower) — use filename_template "{artwork_id}" for the fast id-only path. |
| artsonia_post_commentA | Post a comment on a student's artwork. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). |
| artsonia_invite_fanA | Invite someone (by name + email) to follow a student's Artsonia portfolio. Sends them an invite email. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Use only real addresses you're authorized to invite (test with @example.com). |
| artsonia_set_notificationsA | Turn the account's email opt-ins on/off (news, artist activity, promos). Reads your profile, changes only the opt-in(s) you specify, and re-saves — leaving your name/email/password untouched. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). The preview shows the resulting opt-in state. |
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 15 tools
Most tools target distinct resources (students, portfolios, artwork, comments, fans, feedback, awards, profile, activity), but there is some overlap: artsonia_get_artwork already returns comments, yet artsonia_list_comments exists separately, and artsonia_get_portfolio with include_details duplicates artsonia_get_artwork's data. Descriptions clarify when to use which, so confusion is limited.
All tools use a consistent artsonia_ prefix and snake_case verb_noun pattern (get_, list_, set_, mark_, post_, invite_, download_). The only deviation is artsonia_healthcheck, which is a noun rather than verb_noun, but it remains readable.
15 tools is at the upper end of the ideal 3-15 range but each tool serves a clear purpose in a read-heavy parent account workflow (viewing, downloading, and limited posting). No tool feels redundant enough to remove without losing functionality.
The surface covers the core lifecycle for a parent/fan account: list students, view portfolios/artworks, comments, fans, feedback, awards, profile, notifications, download, post comment, invite fan, and mark feedback read. Minor gaps exist (no update/delete for comments or fans), but these are likely out of scope and agents can work around them.