Skip to main content
Glama
Sign In
ateam-mcp

ateam-mcp

by ariekogan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

ateam_delete_connector

Remove a connector from a deployed solution by stopping and deleting it, removing all references in solution and skill definitions, and cleaning up associated files.

Instructions

Remove a connector from a deployed solution. Stops and deletes it from A-Team Core, removes references from the solution definition (grants, platform_connectors) and skill definitions (connectors array), and cleans up mcp-store files.

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": {
      "solution_id": "<solution_id>",
      "connector_id": "<connector_id>"
    },
    "name": "ateam_delete_connector"
  }
}

Input Schema

NameRequiredDescriptionDefault
solution_idYesThe solution ID (e.g. 'smart-home-assistant')
connector_idYesThe connector ID to remove (e.g. 'device-mock-mcp')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.52

TDQS

A4/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It details the effects: stops connector, deletes from A-Team Core, removes references in solution definition and skill definitions, cleans up mcp-store files. This gives good insight into the operation's impact.

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?

Single sentence with bullet-like list of actions, no fluff. Efficiently conveys all necessary information.

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?

For a delete operation with no output schema, the description fully explains what happens. Could mention if operation is idempotent or error conditions, but overall sufficient.

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 coverage is 100%, so baseline is 3. Description adds examples but no extra semantics beyond what the schema already provides.

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 'Remove a connector from a deployed solution' with specific actions (stops, deletes, removes references, cleans up). Distinct from sibling tools like ateam_create_connector and ateam_delete_skill.

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

Usage Guidelines3/5

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

Implied usage for removing connectors, but no explicit when-to-use or when-not-to-use compared to alternatives. Lacks prerequisites or exclusion criteria.

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