Vigilo MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VIGILO_CLIENT_ID | No | OAuth client ID from the Vigilo Android app. Can alternatively be set in ~/.config/vigilo-connector/config.json. | |
| VIGILO_CLIENT_SECRET | No | OAuth client secret from the Vigilo Android app. Can alternatively be set in ~/.config/vigilo-connector/config.json. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_childrenB | List barna knyttet til den innloggede foresatte, med childId. |
| list_message_threadsB | List beskjedtråder for et barn (bruk childId fra list_children). Returnerer tråder med threadUid, tittel, avsender og tidspunkt. |
| get_message_threadC | Hent alle meldingene i en tråd, inkl. vedleggs-URL-er. |
| read_message_attachmentsA | Last ned og les vedleggene i en meldingstråd (f.eks. ukeplan-PDF). Returnerer utdratt tekst per vedlegg. Bruk dette når en melding har vedlegg (hasAttachments/attachments) og du trenger innholdet — typisk ukeplanen med lekser, turer og «ta med»-beskjeder som ofte legges ved som PDF. |
| api_getA | Rått GET mot foreldre-API-et — for kartlegging av nye endepunkter. path: f.eks. "/api/children". params_json: query-parametre som JSON-objekt; userId legges til automatisk om den ikke er satt. Returnerer status og body uansett utfall, så 404/400 også gir informasjon. |
| web_list_childrenA | List barna med childId og organizationalUnitId (flatet ut). organizationalUnitId (skole/klasse) trengs til timeplan, samtykke og vurdering; childId brukes overalt. Gir også skole- og gruppenavn. |
| news_feedB | Oppslag/«Siste nytt» for et barn. Datoer YYYY-MM-DD (default: siste 30 dager). |
| absencesD | Fravær for et barn. |
| consent_formsC | Samtykkeskjemaer for et barn (krever organizationalUnitId). |
| timetableC | Timeplan/ukesplan for en ISO-uke ("YYYY-WW", default inneværende uke). |
| scheduling_eventsC | Timeplan-hendelser (prøver, aktiviteter) for en ISO-uke ("YYYY-WW"). |
| web_api_getB | Rått GET mot web-foreldreportalen — for kartlegging av nye web-endepunkter. path: f.eks. "/api/absences". params_json: query-parametre som JSON-objekt. Ingen userId legges til (web-API-et bruker childIds/organizationalUnitId). Returnerer status og body uansett utfall. |
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 12 tools
Two pairs of tools overlap significantly: list_children and web_list_children both list children (the latter is a superset), and api_get and web_api_get are both raw GET tools. Descriptions differentiate by API, but an agent may still misselect, especially since web_list_children provides more data.
Tool names mix noun-only (news_feed, absences, timetable), verb_noun (list_children, get_message_thread, read_message_attachments), and noun_verb (api_get, web_api_get) patterns. All are snake_case, but the structural inconsistency makes the set less predictable.
12 tools is well-scoped for a parent portal domain covering children, schedules, messages, and various school data. No tool feels redundant in count, and the raw GET tools add exploration capability without bloat.
The set covers core read operations: children, news, absences, consent, timetable, events, messages, and attachments. An assessment (vurdering) tool is mentioned as needed but missing, and there are no write operations, though the raw GET tools provide a workaround for missing read endpoints.