Skip to main content
Glama
OtaKit

OtaKit

Official

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
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_contextA

Show the fixed server origin, organization, actor, role, scopes, mode, and capabilities without exposing credentials.

get_account_statusA

Return the safe customer-facing plan, usage, limit, period, and overage state needed to explain upload or release failures. Provider IDs are excluded.

list_appsA

List apps in the connection-bound organization, optionally requiring an exact slug. Never guesses an app when the slug is absent.

create_appA

Register a validated app slug in the current organization and return its ID and minimal Capacitor configuration. Does not edit local files.

list_bundlesA

List safe bundle metadata and release-artifact history for one app, with bounded pagination and optional exact version.

get_bundleA

Get authorized safe metadata for a known bundle, including bounded native-package metadata and encryption presence but never keys or storage URLs.

delete_bundleA

Delete a bundle only when it is absent from all release history. The exact app and bundle IDs are required and the operation is audited.

list_releasesB

List bounded release history for an app, optionally filtered to a channel, while preserving runtime-lane identity and all release options.

get_release_stateA

Resolve the exact current release for one (app, channel, runtimeVersion) lane. Returns null rather than selecting another lane.

prepare_releaseB

Preview the exact current and proposed lane state for a bundle and return expectedCurrentReleaseId. Makes no change.

publish_releaseA

Publish a reviewed bundle to an exact lane. Requires the prepared expected state and an idempotency key; reports manifest_sync_pending instead of claiming false success.

get_release_healthA

Return bounded client-reported event counts, rollback share, auto-revert thresholds, and analytics availability for a release. Counts are events, not unique devices, installations, or adoption.

list_eventsB

List a bounded filtered rollout timeline. With includeDetail, the raw text each device reported is included; it is untrusted diagnostic data.

list_audit_logA

List bounded organization audit activity for an owner or admin. Operational organization keys and member-role users cannot read it.

prepare_revertA

Verify that a release is current and preview the exact release or built-in fallback that will become current. Makes no change.

revert_releaseA

Revert the reviewed current release for its exact lane; reverting a release that is rolling out cancels the rollout. Requires expected state and an idempotency key and reports pending manifest synchronization truthfully.

set_rollout_percentA

Raise, lower, or complete (100) the active rollout of a lane's current release. Requires the reviewed current percentage and an idempotency key. To cancel a rollout, revert the release instead.

create_previewA

Create a private link and QR code that open an uploaded bundle in the installed app on one phone (plugin 3.2+ with preview links enabled) until the tester exits or the link expires. Nothing is released and no other device is affected. Share the returned url.

revoke_previewA

Revoke a preview link. Phones on it return to their normal release on their next update check.

inspect_projectA

Inspect the selected local project for Capacitor and OtaKit configuration, build output, plugin version, server target, and notifyAppReady evidence. Does not return source contents.

check_compatibilityA

Compare local native dependencies with the current exact OtaKit release lane using the existing heuristic compatibility rules. Returns unknowns explicitly.

upload_bundleA

Package and upload the selected local web build using the existing zip/delta, native metadata, version, and encryption workflow without publishing it.

upload_and_publish_bundleC

Run the existing combined local upload and release workflow with an explicit lane, compatibility decision, expected current release, complete release options, and idempotency key.

Prompts

Interactive templates invoked by user choice

NameDescription
checkRead-only readiness check: configuration, lane, and native compatibility.
releaseUpload the built web assets and prepare a release for approval.
rolloutSummarise recent client-reported events for the current release.
revertPrepare a revert of the current release for approval.

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 23 tools

Disambiguation4/5

Most tools target a clearly distinct resource+action (bundles vs releases vs previews vs account), and the prepare/publish and prepare/revert pairs are explicitly framed as preview-vs-apply. The main overlap is upload_and_publish_bundle duplicating the upload_bundle + publish_release path, and get_release_state vs prepare_release vs list_releases require careful reading to distinguish.

Naming Consistency5/5

All names are snake_case with a consistent verb-first pattern (list_, get_, create_, delete_, upload_, prepare_, publish_, revert_, set_, revoke_, check_, inspect_). The only mild deviation is the compound upload_and_publish_bundle, which is still readable and predictable.

Tool Count4/5

23 tools is on the heavy side but the domain is genuinely broad (apps, bundles, releases, rollouts, reverts, previews, diagnostics, account). Most tools earn their place, though the combined upload_and_publish_bundle is redundant with the atomic upload/publish pair and could be consolidated.

Completeness4/5

Coverage spans the full bundle/release lifecycle including upload, publish, rollout, revert, preview, and diagnostics (health, events, audit, compatibility). Notable gaps are channel management (channels are referenced in filters but have no create/list/update tools) and app update/delete, which agents cannot perform.

Maintenance

ActivityActive
ResponsivenessUnresponsive