Tiong Creative assistant
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 |
|---|---|
| whats_onA | Everything coming up across the Tiong Creative apps on this Mac within a number of days: overdue and due items, with the app each one belongs to. Start here for "what needs my attention". |
| open_appA | Opens one of the Tiong Creative apps on this Mac so its tools can be used. Only call this after the user has agreed to open it. |
| due_again_itemsA | List items in Due Again (recurring commitments such as renewals, insurance, maintenance and appointments) with their status and next due date. Filter by status or look ahead a number of days. |
| due_again_historyB | The completion history of one Due Again item: when it was done, skipped or rescheduled, and what it cost. |
| due_again_completeA | Record that a Due Again item was done. Due Again then works out the next due date from its schedule. Use the item id from due_again_items. Date defaults to today and cannot be in the future. |
| due_again_add_itemA | Add a new item to Due Again: something that comes due on a date, once or on a schedule (a renewal, a bill, maintenance, an appointment). Give the category by name; if it does not match, the reply lists the categories to choose from. Reminders are days before the due date. |
| gift_keeper_upcomingA | Upcoming occasions in Gift Keeper (birthdays, anniversaries, holidays and custom dates) with who they are for, whether a gift has been chosen, the budget and what has been spent so far. |
| gift_keeper_peopleB | The people in Gift Keeper with what helps choose a gift: relationship, interests, sizes, preferences and things to avoid. Give a name for one person, or leave it out for everyone. |
| gift_keeper_add_ideaA | Save a gift idea in Gift Keeper for a person, by name. If the name does not match, the reply lists the people to choose from. Optional link, price, notes and priority. |
| gift_keeper_mark_gift_givenB | Mark a gift in Gift Keeper as given. Use a gift id from gift_keeper_upcoming. |
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 10 tools
Each tool targets a distinct resource+action, cleanly separated by domain prefix (due_again_*, gift_keeper_*) plus the two general tools whats_on and open_app. whats_on is an aggregate dashboard while due_again_items/gift_keeper_upcoming are domain-specific lists, and the descriptions make that boundary clear.
The app-prefixed snake_case pattern (due_again_items, gift_keeper_add_idea) is used consistently and predicatively throughout. whats_on and open_app deviate by having no app prefix, a minor but noticeable inconsistency in an otherwise uniform scheme.
Ten tools across two apps plus a general entry point and an app-opener is well-scoped; each tool earns its place in the read/write flow. No bloat or redundancy in the count.
Core workflows are covered, but there are notable gaps: no update/edit or delete for Due Again items, and Gift Keeper cannot add people or occasions (only list them and record gift ideas/given status). Agents will hit dead ends for editing or creating people/occasions.