Skip to main content
Glama

ateam-mcp

by io.github.ariekogan

ateam_delete_connector

⚠️ CASCADING — any skill whose engine.bootstrap_tools or tools[] name a tool from this connector will FAIL its next execution. Stops and deletes the connector from A-Team Core; drops references from the solution definition (grants, platform_connectors, ui_plugins ids starting mcp:<connector-id>:*) and skill definitions (connectors array); cleans up mcp-store files. ALSO REMOVES THE SOURCE: connectors/<id>/ is deleted from the repo (main AND dev) in the same call, so the delete is DURABLE. This CHANGED on 2026-08-23 — it used to preserve the source and name ateam_build_and_run(github:true) as a way to resurrect. That made a delete undo itself on a later publish, and only in some states, since connectors[] is synthesized from mcp_store keys ONLY when it is empty. If you want the code kept, copy it out (ateam_get_connector_source) BEFORE deleting. If the repo removal fails the response says so under github — Core is clean but the source is still there. REQUIRES confirm:true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmYesREQUIRED. Must be exactly true. A missing/false value refuses the call with a recovery hint.
solution_idYesThe solution ID (e.g. 'smart-home-assistant')
connector_idYesThe connector ID to remove (e.g. 'device-mock-mcp')

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries full burden and excels: it discloses the CASCADING destructive effect, the durable repo deletion, the 2026-08-23 behavior change, the partial-failure reporting under `github`, and the confirm requirement. Nothing about the tool's side effects is hidden.

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?

The text is long but front-loads the critical warning and then systematically covers effects, durability, alternative, and failure case. It is slightly verbose with historical detail, but every sentence contributes essential caveats for a destructive operation.

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?

For a high-risk, cascading, no-output-schema tool with zero annotations, the description covers all key operational aspects: what will break, what gets deleted, how to preserve code, failure response semantics, and the required confirmation flag. An agent can safely invoke this tool with minimal ambiguity.

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?

The schema already documents all three parameters with examples and a strict confirm rule (100% coverage), so the description adds little beyond re-emphasizing confirm:true. Baseline 3 applies because the schema does the heavy lifting.

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 precise verb and resource — 'Stops and deletes the connector from A-Team Core' — and enumerates the full scope (references, mcp-store files, source repo). It is unmistakably distinct from siblings like ateam_delete_skill or ateam_get_connector_source.

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?

It clearly frames when to use the tool: when a durable, cascading delete is intended, and explicitly routes to ateam_get_connector_source if the code must be kept. It also cautions against relying on the old resurrection path, giving an agent the context needed to decide between delete and preserve.

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

All ateam-mcp 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

A3.9/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, with detailed descriptions that differentiate similar functions like chain polling vs. chain inspection. However, there is slight overlap between ateam_design_advisor, ateam_get_spec, and ateam_spec_search, which all serve design guidance, potentially causing confusion if descriptions are not read carefully.

Naming Consistency4/5

The naming mostly follows a consistent verb_noun pattern with the 'ateam_' prefix (e.g., ateam_get_solution, ateam_create_connector, ateam_test_skill). Minor deviations include ateam_patch (missing object) and ateam_redeploy (verb only), but overall the pattern is predictable and clear.

Tool Count3/5

With 47 tools, the count is high and exceeds the typical 15-tool threshold for a well-scoped set. However, the tools cover a broad and complex platform (auth, deployment, testing, GitHub integration, scaffolding), and each tool appears to have a distinct role, making the count borderline acceptable rather than excessive.

Completeness4/5

The tool set covers the full lifecycle of building, deploying, testing, and managing A-Team solutions, including design, GitHub integration, and verification. Minor gaps exist, such as no explicit tool for deleting individual files (though patching can overwrite) and no standalone skill listing, but these are not critical dead ends for an agent.

Resources