Skip to main content
Glama

scalingo

by io.usefulapi

Trigger a deployment

trigger_deployment
Destructive

MUTATES Scalingo infrastructure — triggers a new deployment from a source archive URL (a tar.gz reachable by Scalingo). To roll back, re-deploy a previous git_ref/archive — there is no separate rollback endpoint. Scalingo API: POST /v1/apps/{app}/deployments. Returns { deployment }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appYesThe app name (e.g. my-production-app) or app id (app-…).
git_refNoOptional git reference label for the deployment (branch/tag/SHA).
source_urlYesURL of the source archive (tar.gz) Scalingo should build and deploy.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare destructiveHint=true, and description reinforces mutation with 'MUTATES' and mentions API method POST. Adds context about archive format and return structure. Does not contradict annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Highly concise: two sentences plus API endpoint. No redundant information. Front-loaded with 'MUTATES' for quick comprehension.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose, usage guidance, and return format despite no output schema. Could mention deployment trigger behavior (immediate/asynchronous), but overall complete for a trigger tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and description adds value by specifying archive format ('tar.gz') and the purpose of git_ref for rollback, beyond the schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the verb 'triggers a new deployment' and the resource 'Scalingo infrastructure' with the source archive URL. Distinguishes from sibling tools like list_deployments by focusing on mutation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit guidance on rollback usage, stating there is no separate endpoint, and implies to use this tool with a previous git_ref/archive. Could be clearer on when not to use, but sufficient.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All scalingo toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation5/5

Each tool targets a distinct resource or action: get_app vs get_app_logs vs get_app_stats are clearly different; list_addon_providers vs list_addons differentiate available vs provisioned. Mutation tools (restart, scale, trigger_deployment, set_variables) are unique. The fallback scalingo_request is a separate generic GET. No confusion between tools.

Naming Consistency4/5

All tools use snake_case with a verb_noun pattern (get_, list_, restart_, scale_, trigger_, set_). The only exception is 'scalingo_request' which breaks the pattern, but it is clearly documented as a power-user escape hatch. Overall very consistent.

Tool Count5/5

21 tools is well-scoped for a PaaS platform covering core resources like apps, deployments, addons, domains, env variables, and collaborators. It covers the essential operations without being bloated; each tool serves a clear purpose.

Completeness2/5

The toolset is heavily read-oriented; mutations are limited to restart, scale, set_variables, and trigger_deployment. Missing CRUD for major resources: no create/delete app, add/remove collaborators, add/remove domains, provision/delete addons, or update app settings. Agents will face dead ends when needing to perform writes beyond the few covered.

Resources