Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
NUCLEUS_SWIFTNoPath to the swift executable.
NUCLEUS_SWIFTCNoPath to the swiftc executable.
NUCLEUS_APPLE_MCP_CACHE_DIRNoOverrides the cache directory for Swift sidecar builds.

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
tasks
{
  "list": {},
  "cancel": {},
  "requests": {
    "tools": {
      "call": {}
    },
    "prompts": {
      "get": {}
    },
    "resources": {
      "read": {}
    }
  }
}
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
calendar.list_sourcesA

List calendar sources/accounts.

calendar.list_calendarsC

List event calendars.

calendar.list_eventsB

List events within a time range.

calendar.create_eventC

Create a calendar event.

calendar.update_eventC

Update an existing calendar event.

calendar.delete_eventB

Delete a calendar event.

health.read_daily_metricsA

Read one day's exported Health metrics snapshot from an S3-compatible object store.

health.read_range_metricsA

Read a date range of exported daily metrics using monthly indexes. Missing dates are reported, not treated as an error.

health.analyze_rangeA

Analyze a Health date range using exported daily snapshots only. Returns metric summaries, segment trends, notable days, and brief insights without reading raw samples.

health.list_sample_catalogA

List known Health raw sample types, kinds, tags, and how they relate to daily metrics.

health.read_samplesB

Read raw Health samples across one or more dates, filtered by type_keys/tags/kinds, with manifest-aware pagination.

health.read_daily_rawA

Read one day's raw Health samples. Prefer health.read_samples for range queries and richer filtering.

health.inspect_dayA

Inspect one day by combining the daily snapshot with the raw manifest, and explain metric/raw gaps.

health.list_changesA

List health sync commits after an optional cursor, with optional per-date raw type details from raw manifests.

notes.list_accountsB

List Notes accounts.

notes.list_foldersC

List Notes folders.

notes.list_notesB

List notes (metadata-first).

notes.get_noteB

Fetch a note with optional content and attachments.

notes.create_noteC

Create a new note.

notes.update_noteC

Update an existing note.

notes.delete_noteA

Delete a note.

notes.list_attachmentsB

List attachments for a note.

notes.save_attachmentB

Export an attachment to a file path.

notes.add_attachmentC

Add attachment(s) to a note from local file paths.

reminders.list_sourcesB

List reminder sources/accounts.

reminders.list_listsC

List reminder lists.

reminders.list_remindersC

List reminders by filters.

reminders.create_reminderC

Create a reminder.

reminders.update_reminderB

Update an existing reminder.

reminders.delete_reminderB

Delete a reminder.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 30 tools

Disambiguation5/5

Tools are clearly separated by domain prefixes (calendar, health, notes, reminders) and specific verb-noun combinations within each domain, eliminating any ambiguity between tools.

Naming Consistency5/5

All tools follow a consistent pattern of domain prefix followed by verb_noun in snake_case, e.g., calendar.create_event, health.read_samples, notes.list_folders, providing a highly predictable naming scheme.

Tool Count4/5

With 30 tools across four distinct domains (calendar, health, notes, reminders), the count is above average but well-justified by the breadth of functionality, averaging 7.5 tools per domain which is reasonable for feature-rich integrations.

Completeness5/5

Each domain provides comprehensive CRUD-like operations plus additional utilities: calendar covers events/sources, health includes analysis and raw data reads, notes cover attachments and folders, and reminders cover lists/sources. No obvious gaps for typical use cases.

Maintenance

ActivityInactive
ResponsivenessUnresponsive