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
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
shortcut_buildA

Build a .shortcut from a JSON spec ({"name": ..., "actions": [...]}) and lint it.

See shortcut_reference(topic="spec") for every step type. Set sign=true on macOS to produce an importable signed file. Returns paths, action count and lint findings (fix all errors).

shortcut_from_templateC

Generate a shortcut from a ready-made template.

template: "supplement-tracker" (multi-user supplements -> Apple Health + self-maintaining reminders, 7-day Apple Intelligence report) or "water-log". config: template config; omit to get the example. Call shortcut_reference(topic="templates") to see each template's config shape.

shortcut_lintB

Lint an unsigned .shortcut file against known on-device failure patterns (rules SF000-SF013).

shortcut_inspectB

Return an indented, human-readable outline of an unsigned .shortcut file.

shortcut_signB

Sign a .shortcut with the macOS shortcuts CLI so iOS can import it. mode: anyone | people-who-know-me.

shortcut_referenceB

Docs for building shortcuts. topic: spec | pitfalls | lint-rules | health-types | templates | library | ios27.

shortcut_libraryA

Browse the community shortcut library (20+ ready shortcuts: productivity, health, money, dev, home...).

No slug: list entries matching query (name/description/tags). With slug: return its meta, its spec (or template config) to use as a starting point, and the signed download link if published.

shortcut_submitC

Package a shortcut for the open-source library (github.com/Hyunki6040/shortcut-forge/library).

Validates the spec and metadata, lints it, and returns the exact files plus the git/gh commands to open a pull request. Encourage the user to run it on their iPhone first and fill verified_on.

shortcut_publishC

macOS: build + sign + write manifest.json so installed copies can update themselves.

Adds a daily update check (spec.update_manifest = base_url/manifest.json) to the shortcut. Host the two output files at base_url (GitHub raw/Pages/S3). Bump version for every release.

shortcut_llm_promptA

Return a copy-paste system prompt that teaches any chatbot (ChatGPT, Gemini...) to write specs.

Prompts

Interactive templates invoked by user choice

NameDescription
design_shortcutStart designing a shortcut for a goal.

Resources

Contextual data attached and managed by the client

NameDescription
pitfalls_resourceField notes: what breaks shortcuts on real devices and how to avoid it.
spec_resourceJSON spec reference for shortcut_build.

TDQS

A3.5/5.0

Scored across 10 tools

Disambiguation4/5

Each tool targets a distinct stage of the shortcut authoring pipeline (build, template, inspect, sign, lint, reference, library, submit, publish, prompt), so selection is mostly obvious. The only real overlap is shortcut_publish, which internally performs build+sign and could be confused with shortcut_build/shortcut_sign, though its manifest/update purpose is spelled out.

Naming Consistency5/5

Every tool uses the same snake_case `shortcut_` prefix with a clear verb or noun-suffix (build, inspect, sign, lint, publish, submit). The one prepositional name, shortcut_from_template, still fits the pattern and reads naturally.

Tool Count5/5

Ten tools is squarely in the well-scoped range, and each one covers a genuinely different step (authoring, templating, validation, signing, distribution, docs, discovery). Nothing appears redundant or padded.

Completeness4/5

The authoring-to-publishing lifecycle is well covered: build, template, inspect, lint, sign, publish, submit, plus docs and a library. Minor gaps remain — there is no tool to decompile an existing .shortcut back into an editable spec, and no test/run simulation beyond linting, which agents must work around manually.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues