Skip to main content
Glama
ariekogan

ateam-mcp

by ariekogan
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Hybrid

ateam_build_and_run

Deploy the main branch to A-TEAM Core with validation, health-checks, and optional testing—automatically pushes changes to GitHub.

Instructions

DEPLOY THE CURRENT MAIN BRANCH TO A-TEAM CORE. ⚠️ HEAVIEST OPERATION (60-180s): validates solution+skills → deploys all connectors+skills to Core (regenerates MCP servers) → health-checks → optionally runs a warm test → auto-pushes to GitHub.

🌳 DEV/PROD WORKFLOW:

  1. Edit files → ateam_github_patch (writes to dev branch by default)

  2. (Optional) Preview what's about to ship → ateam_github_diff

  3. Ship dev → main → ateam_github_promote (merges + auto-tags prod-YYYY-MM-DD-NNN)

  4. Deploy main to Core → ateam_build_and_run

This tool ALWAYS deploys the main branch — there is no ref parameter. To deploy in-progress dev work, first promote it.

AUTO-DETECTS GitHub repo: if you omit mcp_store and a repo exists, connector code is pulled from main automatically. First deploy requires mcp_store. After that, edit via ateam_github_patch + promote, then build_and_run. For small changes prefer ateam_patch (faster, incremental). Requires authentication.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
solution_idNoThe solution ID. Use this INSTEAD of passing the full solution object — the solution definition is auto-pulled from main. Required if solution object is omitted.
solutionNoFull solution definition. Required on first deploy. After first deploy, just pass solution_id instead — everything is auto-pulled from GitHub main.
skillsNoOptional after first deploy: skill definitions. If omitted, auto-pulled from main (skills/{id}/skill.json).
connectorsNoOptional: connector metadata (id, name, transport). Entry points auto-detected from mcp_store.
mcp_storeNoOptional: connector source code files. Key = connector id, value = array of {path, content}.
githubNoOptional: if true, pull connector source code from main. AUTO-DETECTED: if you omit both mcp_store and github, the system checks if a repo exists and pulls from main automatically.
test_messageNoOptional: send a test message after deployment to verify the skill works. Returns the full execution result.
test_skill_idNoOptional: which skill to test (defaults to the first skill).

Tool Definition Quality

A4.8/5.0
Behavior5/5

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

No annotations provided, so description carries full burden. It discloses the heaviest operation duration (60-180s), validation, deployment to Core, health checks, optional warm test, auto-push to GitHub, and authentication requirement. No contradictions.

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

Conciseness4/5

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

Description is somewhat long but well-structured with emojis, bullet points, and clear sections. Front-loaded with key purpose and warnings. Some repetition could be trimmed, but every sentence adds value.

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

Completeness5/5

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

Covers all aspects: workflow, parameter usage (first deploy vs subsequent), auto-detection, alternatives (ateam_patch), prerequisites (authentication), and outcome (deployment + GitHub push). No output schema, but return behavior is implied through test_message. Complete for a complex deployment 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%, so baseline is 3. Description adds significant value: explains auto-detection of repo, first deploy vs subsequent behavior, and clarifies that parameters like solution, skills, connectors, and mcp_store are optional after first deploy. This contextual information enhances understanding 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 clearly states the purpose: 'DEPLOY THE CURRENT MAIN BRANCH TO A-TEAM CORE.' It distinguishes from siblings like ateam_github_patch, ateam_github_promote, and ateam_patch, specifying that this is for deploying the main branch after promotion.

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

Usage Guidelines5/5

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

Provides a detailed DEV/PROD workflow (steps 1-4) and explicit guidance: 'This tool ALWAYS deploys the `main` branch' and 'To deploy in-progress dev work, first promote it.' Also advises preferring ateam_patch for small changes, making when-to-use clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ariekogan/ateam-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server