Skip to main content
Glama

Remove my subscription connection

remove_subscription
DestructiveIdempotent

Disconnect one of your provider subscriptions from this workspace. Never send authorization secrets through MCP.

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": {
      "workspace_id": "<workspace_id>",
      "connection_id": "<connection_id>"
    },
    "name": "remove_subscription"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspace_idYesThe workspace id (from whoami).
connection_idYesYour connection id from list_subscriptions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered structurally. The description adds only a security warning ("Never send authorization secrets through MCP") and does not say what is actually lost on disconnect — stored credentials, historical usage data, or provider-side revocation. It adds some context but not the operational consequences an agent would want before a destructive call.

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?

Two short sentences with the action front-loaded and no filler. The second sentence is a security aside that is only loosely tied to this specific operation, keeping it just under a top score.

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?

For a destructive, two-parameter tool with full schema coverage and annotations declaring destructiveness and idempotency, the definition covers the essentials. It is incomplete on consequences — whether the disconnect is reversible, what happens to existing usage history, and whether provider-side tokens are revoked — which matters for a destructive operation.

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%, and both parameters are documented in-schema with provenance hints (whoami for workspace_id, list_subscriptions for connection_id). The description adds no further meaning about either parameter, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: "Disconnect one of your provider subscriptions from this workspace." That clearly distinguishes it from connect_subscription (the inverse) and from list_subscriptions. It stops short of naming any sibling explicitly, so it lands at 4 rather than 5.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool versus alternatives such as connect_subscription, list_subscriptions, or remove_member, and no stated prerequisites (e.g., ownership or admin rights needed to disconnect a workspace connection). Usage is only inferable from the name and the word "Disconnect."

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