Skip to main content
Glama

Destroy a connector

destroy_connector
DestructiveIdempotent

Destroy an organization connector and its stored credential. This cannot be undone, so confirm with the user first. A connector that any website, app, or agent still holds is refused, and the answer names each holder: free each with detach_connector, then destroy it. A connector an agent owns is not an organization connector; the answer says what removes it. Destroying a connector that is already gone changes nothing. Requires connecting a Valet account.

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": {
      "connector": "<connector>"
    },
    "name": "destroy_connector"
  }
}

Input Schema

NameRequiredDescriptionDefault
org_nameNoThe Valet organization the connector belongs to. Omit to use the organization the account joined first.
connectorYesThe connector's name in the organization.

Output Schema

NameRequiredDescriptionDefault
orgYesName of the Valet organization the call acted in.
kindYesAlways connector: the kind of thing this tool destroys.
nameYesName of the connector destroyed.
already_goneNoTrue when the connector was already gone before the call, so nothing was destroyed. Absent when this call destroyed it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedOutput schema / properties / already_gone / description
      Previous value: -"True when the thing was already gone before the call, so nothing was destroyed. Absent when this call destroyed it."New value: +"True when the connector was already gone before the call, so nothing was destroyed. Absent when this call destroyed it."
    • changedOutput schema / properties / kind / description
      Previous value: -"What the thing was, such as channel, connector, or resource."New value: +"Always connector: the kind of thing this tool destroys."
    • addedOutput schema / properties / kind / enum
      Added value: +[
      +  "connector"
      +]
    • changedOutput schema / properties / name / description
      Previous value: -"Name of the thing the call destroyed, as the caller gave it."New value: +"Name of the connector destroyed."
  2. Changed5 schema fields changed
    • changedInput schema / properties / connector / description
      Previous value: -"Required. The connector's name in the organization."New value: +"The connector's name in the organization."
    • addedOutput schema / properties / already_gone / description
      Added value: +"True when the thing was already gone before the call, so nothing was destroyed. Absent when this call destroyed it."
    • addedOutput schema / properties / kind / description
      Added value: +"What the thing was, such as channel, connector, or resource."
    • addedOutput schema / properties / name / description
      Added value: +"Name of the thing the call destroyed, as the caller gave it."
    • addedOutput schema / properties / org / description
      Added value: +"Name of the Valet organization the call acted in."
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "already_gone": {
      +      "type": "boolean"
      +    },
      +    "kind": {
      +      "type": "string"
      +    },
      +    "name": {
      +      "type": "string"
      +    },
      +    "org": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "org",
      +    "name",
      +    "kind"
      +  ],
      +  "type": "object"
      +}
  4. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructive=true and idempotent=true, but the description adds real value beyond them: the stored credential is destroyed too, the operation is irreversible, a refused call names every holder, and an auth prerequisite (Valet account) is stated. This is strong coverage; it stops short of only minor details such as scope of propagation or audit side effects.

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?

Front-loaded with the destructive action and its irreversibility, then the refusal and fallback path. Every sentence carries information, though a couple of clauses are compressed to the point of being cryptic, e.g. 'the answer says what removes it.'

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?

Output schema exists, yet the description still usefully previews what a refused call returns (the holders' names). Irreversibility, idempotency, auth requirement, and the detach-first recovery path are all present, so nothing an agent needs before calling is missing.

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 100%, including the default-organization fallback for org_name and the connector name semantics, so the schema already carries the parameter burden. The description adds no format, syntax, or edge-case guidance for either parameter, so the baseline applies.

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?

States a specific verb and resource: 'Destroy an organization connector and its stored credential.' It also scopes the object (organization connector, not agent-owned), which separates it from detach_connector and from any agent-owned-connector case.

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?

Gives explicit preconditions and routing: confirm with the user first, free holders with detach_connector before retrying, and note that agent-owned connectors are a different case entirely. When-to-use and when-not-to-use are both covered with named alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources