Tools Reference
Every tool exposed by the Stallion MCP server — navigation and analytics — with inputs and what each returns. All read-only.
Tools Reference
The Stallion MCP server exposes a small set of consolidated, read-only tools. Your
assistant picks the right ones automatically — you rarely call them by name. Project-scoped
tools accept names or ids; pass org to disambiguate a project name that exists in
more than one organization.
Read-only:
Every tool observes; none of them change a release, bundle, or setting. You only ever see what your own Stallion account can access.
Navigation
These tools let the assistant find its way around your account by name.
| Tool | Inputs | Returns |
|---|---|---|
list_orgs | — | Your organizations (id, name, region) |
list_projects | org | Projects in an org, with platform flags |
get_project_detail | project, org? | Project config: platforms, patch/backup-CDN, archive state (no secrets) |
list_buckets | project, org? | Buckets in a project, with latest bundle versions |
list_bundles | bucket, project, org? | Bundles in a bucket: version, size, author, promoted, checksum |
list_app_versions | project, platform, org? | App versions that have releases, with counts — a good place to start |
list_releases | project, platform, appVersion, org? | Production releases and their rollout state |
Analytics
These tools answer release-health questions.
| Tool | Inputs | Returns |
|---|---|---|
get_rollout_health (headline) | project, platform, appVersion, org? | Adoption + rollback metrics and a recommendation (advance / hold / rollback / investigate) with the reason |
get_adoption_trend | project, platform, appVersion, range | Download → install → rollback time series (1D / 7D / 15D / 1M) with drop-off at each step |
diagnose_rollback | project, platform, appVersion, range | The top crash clusters behind auto-rollbacks |
get_patch_info | project, platform, appVersion, org? | Delta-patch sizes for a release vs the full-bundle download |
Utility
| Tool | Inputs | Returns |
|---|---|---|
auth_status | — | Confirms your token works and reports the signed-in user |
The headline tool
get_rollout_health is the one to reach for on every rollout. It joins adoption rate,
rollback rate, and live rollout state into a single verdict:
- advance — metrics are healthy; safe to increase the rollout percentage.
- hold — not enough exposure yet, or early warning signs; wait and watch.
- rollback — rollback rate is over threshold; pull the release.
- investigate — the release is paused or already rolled back; look closer.
Every response includes the raw numbers alongside the recommendation, so you can see exactly why the verdict was reached.
Tip:
Not sure where to start? Ask "which app versions have releases for my project?" —
that runs list_app_versions and gives you the versions to drill into.