Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_memoryA

Search Sara's long-term memory about the owner (facts, summaries of past conversations, decisions, promises, dates) by words and meaning. Use it for context about the owner's life, preferences and projects; use list_facts to browse all facts, search_library for documents, and list_recent_conversations for what was talked about lately. Returns plain text, one note per line: "- [kind, YYYY-MM-DD] text", best match first, or a line saying nothing was found. Read-only. Never includes other people's chats, private conversations or (while Adult mode is off) anything explicit.

list_factsA

List the facts Sara has learned about the owner (name, people, likes, habits, work), newest first. Use it to get a general picture of the owner; use search_memory to find something specific, and remember_fact to add a fact. Returns plain text, one fact per line: "- [fact, YYYY-MM-DD] text", or "No notes yet." Read-only; facts from other people's chats and private conversations are never included.

list_recent_conversationsA

List the owner's most recent conversations with Sara, newest first, each with its title, when it was last active and a short summary when she has one. Use it to see what the owner has been talking about lately; use search_memory to look for a topic across all of her memory. Returns plain text, one conversation per line: "- Title (last ): summary", or "No conversations yet." Read-only. Never lists other people's chats, private, archived or imported conversations.

get_todayA

Get the owner's agenda for today in one view: to-dos due today or overdue (and high-priority ones without a date), reminders in the next 24 hours, calendar events when a calendar is connected, and birthdays or other dates that matter coming up. Use it for "what's on today"; use list_tasks for the whole to-do list with filters. Returns plain text: the date, then sections "To-dos:" ("- #id title (due …)"), "Reminders:", "Calendar:" and "Coming up:". The #ids work with complete_task, update_task and delete_task. Read-only; takes no input.

list_tasksA

List the to-dos in the owner's planner in Sara, optionally only open or done ones, or one project. Use it to see the whole to-do list or find a to-do's id; use get_today for just what's due today. Returns plain text, up to 100 lines, open ones first by priority and due date: "- #id [ ] title (priority) due [project]" ([x] when done), or "Nothing open." The #id is what complete_task, update_task and delete_task take. Read-only.

search_libraryA

Search the documents the owner keeps in Sara's library (PDFs, Word files, spreadsheets, books, saved web pages) by words and meaning. Use it for questions answered by the owner's documents; use search_memory for what Sara remembers from conversations. Returns up to 6 passages (each up to 1,400 characters), each headed by "[document title, place]" (page or section), or a line saying nothing was found. Read-only; documents shared in a single chat only are left out.

list_notesA

List the notes in the owner's planner in Sara (titles only), newest first, or the ones matching some words. Use it to find a note's id; then read it with read_note, change it with update_note or remove it with delete_note. Returns plain text, up to 100 lines: "- #id title [project] (updated YYYY-MM-DD)", or "No notes." Read-only.

read_noteA

Read one note from the owner's planner in Sara, in full, by its id. Use list_notes first to find the id. Returns the note as Markdown: "# Title", a blank line, then the text. An unknown id returns an error. Read-only.

ask_saraA

Send Sara a message and get her reply, as in a chat: she answers with her memory and personality in a conversation kept for this app, which the owner can read in Sara. Use it for questions, opinions or anything conversational; to store a fact on purpose use remember_fact, and to change the planner use the to-do and note tools. Returns her reply as plain text (with the AI notice when a new session starts). If her own tools are allowed for other apps and one needs the owner's OK, it returns a note that it is waiting for approval in Sara. Can take up to a few minutes; one key can have two replies running at once.

add_taskA

Add a new to-do to the owner's planner in Sara, with an optional due time, project and priority. Use update_task to change an existing one. Returns "Added to-do #id: title" (the #id works with complete_task, update_task and delete_task). A due time without an hour means 9:00 in the owner's time zone. Only listed when the owner turns on "Let other apps change things" in Sara. Follows the owner's approval setting for her todo tool (allowed, ask first, or off): when it asks first, it returns "Waiting for approval in Sara" and nothing changes until the owner presses Allow there; when it is off, it returns that it's turned off.

complete_taskA

Mark one of the owner's to-dos in Sara as done, by its id (from list_tasks or get_today). Use update_task with status "open" to reopen one. Returns "Done: to-do #id title". Marking a to-do that is already done changes nothing. Only listed when the owner turns on "Let other apps change things" in Sara. Follows the owner's approval setting for her todo tool (allowed, ask first, or off): when it asks first, it returns "Waiting for approval in Sara" and nothing changes until the owner presses Allow there; when it is off, it returns that it's turned off.

update_taskA

Change one of the owner's to-dos in Sara by its id (from list_tasks or get_today): its title, due time, project, priority, details or status. Only the fields you give change; the rest stay as they are. Use complete_task to simply tick one off. Returns "Changed to-do #id: title" with the new due time. Only listed when the owner turns on "Let other apps change things" in Sara. Follows the owner's approval setting for her todo tool (allowed, ask first, or off): when it asks first, it returns "Waiting for approval in Sara" and nothing changes until the owner presses Allow there; when it is off, it returns that it's turned off.

delete_taskA

Delete one of the owner's to-dos from Sara's planner for good, by its id (from list_tasks or get_today). This can't be undone; to tick a to-do off instead, use complete_task. Returns "Deleted to-do #id: title". Only listed when the owner turns on "Let other apps change things" in Sara. Deleting always waits for the owner: it returns "Waiting for approval in Sara" and nothing changes until the owner presses Allow there (even when her todo tool is set to allowed); when that tool is off, it returns that it's turned off.

add_noteA

Save a new note (a title and free text, Markdown welcome) in the owner's planner in Sara, optionally in a project. Use update_note to change an existing note and remember_fact for a single fact about the owner. Returns "Saved note #id: title" (the #id works with read_note, update_note and delete_note). Only listed when the owner turns on "Let other apps change things" in Sara. Follows the owner's approval setting for her note tool (allowed, ask first, or off): when it asks first, it returns "Waiting for approval in Sara" and nothing changes until the owner presses Allow there; when it is off, it returns that it's turned off.

update_noteA

Change one of the owner's notes in Sara by its id (from list_notes): its title, its text (replaced as a whole) or its project. Only the fields you give change. Read the note with read_note first if you mean to edit part of the text. Returns "Changed note #id: title". Only listed when the owner turns on "Let other apps change things" in Sara. Follows the owner's approval setting for her note tool (allowed, ask first, or off): when it asks first, it returns "Waiting for approval in Sara" and nothing changes until the owner presses Allow there; when it is off, it returns that it's turned off.

delete_noteA

Delete one of the owner's notes from Sara's planner for good, by its id (from list_notes). This can't be undone. Returns "Deleted note #id: title". Only listed when the owner turns on "Let other apps change things" in Sara. Deleting always waits for the owner: it returns "Waiting for approval in Sara" and nothing changes until the owner presses Allow there (even when her note tool is set to allowed); when that tool is off, it returns that it's turned off.

remember_factA

Ask Sara to remember one fact about the owner in her long-term memory, marked as told by this app. Use it to store something on purpose (ask_sara is for conversation, and she may or may not keep what is said there); use add_note for longer text. Returns "Remembered (#id): fact" once the owner allows it. Only listed when the owner turns on "Let other apps change things" in Sara, and it always asks first: it returns "Waiting for approval in Sara" and nothing is stored until the owner presses Allow there.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 17 tools

Disambiguation4/5

Most tools target a distinct resource+action, and descriptions explicitly disambiguate close calls (get_today vs list_tasks, complete_task vs update_task, ask_sara vs remember_fact). The read-only memory cluster (search_memory, list_facts, list_recent_conversations, search_library) has some conceptual proximity but is well-differentiated by descriptions.

Naming Consistency5/5

All names follow a consistent verb_noun pattern: read_note, list_tasks, search_memory, add_task, update_note, delete_note, remember_fact, ask_sara. No mixed casing or stray styles.

Tool Count4/5

17 tools for a broad personal-assistant domain (tasks, notes, memory, library, conversations, chat) is slightly heavy but every tool maps to a real operation. It sits just above the comfortable 3-15 range without feeling padded.

Completeness4/5

Tasks and notes have full CRUD coverage with clear lifecycle. Memory and library are lighter (remember_fact exists but no update/delete fact; search_library has no add-document), but these are reasonable gaps an agent can work around.

Maintenance

ActivityMaintained
ResponsivenessResponsive