Skip to main content
Glama
Sign In
flutter-orchestrator

flutter-orchestrator

by peter14l
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

generate_flutter_cicd_pipeline

Generate production CI/CD pipelines for Flutter apps, with split APK builds, keystore signing, Windows MSIX packaging, and Fastlane deployment lanes.

Instructions

Generates production multi-platform GitHub Actions workflows for Flutter with Split-per-ABI signed APKs, automated 'gh secret set' keystore script, Windows MSIX packaging with self-signed test certificates, and Fastlane.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectName": "<projectName>"
    },
    "name": "generate_flutter_cicd_pipeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectNameYesProject name.
enableFastlaneNoGenerate Fastlane release lanes for TestFlight & Play Store.
enableWebDeployNoEnable Flutter Web build step.
targetPlatformsNo
enableWindowsMsixNoBuild and sign Windows MSIX with a test certificate.
enableSplitPerAbiApkNoBuild split per ABI release APKs (armeabi-v7a, arm64-v8a, x86_64).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are present, so the description carries the full burden. It discloses key generated outputs and specifics such as signed APKs, self-signed MSIX certificates, and Fastlane. However, it does not state whether files are created/overwritten, whether GitHub CLI/secrets are prerequisites, or what side effects occur.

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?

A single dense sentence front-loads the core purpose before enumerating major features. There is no filler, repetition of the tool name, or unnecessary explanation.

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

Completeness3/5

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

The description gives enough detail for an agent to select the tool and understand its main outputs, but with no output schema and no annotations, it omits operational details like where workflows are written, whether existing files are overwritten, and what external tools are required. These gaps matter for a generator tool of this complexity.

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

Parameters3/5

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

Schema description coverage is high (83%), so the schema already documents most parameters. The description adds context by tying split-per-ABI, MSIX, and Fastlane directly to the generated workflow, but it does not meaningfully clarify parameter values beyond the schema.

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?

The description states a specific verb ('Generates'), a clear resource ('GitHub Actions workflows for Flutter'), and enumerates concrete artifacts such as split-per-ABI APKs, keystore scripts, MSIX packaging, and Fastlane. It is distinctive among the sibling tools, none of which claim CI/CD workflow generation.

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?

The description makes the context clear: this is the tool for production, multi-platform Flutter CI/CD pipeline generation. It does not explicitly name exclusions or alternatives, but the purpose is unambiguous enough for an agent to know when to invoke it.

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

Deploy Server

Other Tools