alterlab-mcp-server

Disable Beta Feature

alterlab_disable_beta_feature

Idempotent

Opt out of a beta feature on your AlterLab account by providing its slug; repeated calls succeed even if already disabled, and generally available features cannot be turned off.

Instructions

Opt out of a beta feature on your AlterLab account. This operation is idempotent — calling it when not opted in returns success. GA (generally available) features cannot be disabled.

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": {
      "slug": "<slug>"
    },
    "name": "alterlab_disable_beta_feature"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	URL-safe slug of the beta feature to opt out of (e.g., 'v2-extraction', 'stealth-v3'). Use alterlab_list_my_beta_features to see your currently active slugs.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.5.0Jun 12, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, so the idempotency sentence itself is largely redundant. However, the description adds genuine value beyond the annotations: the no-op call returns success rather than erroring, and GA features are rejected outright — both are real behavioral facts an agent would otherwise have to discover.

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, front-loaded sentences with no filler — the operation statement comes first and the constraints follow. Minor deduction because the idempotency clause restates an annotation, though it does carry the extra "returns success" detail.

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 one-parameter mutation with full schema coverage and four annotation hints, this is close to complete: intent, no-op behavior, and the GA rejection case are all covered. What remains unstated is the failure mode for an unknown slug and the shape of a successful response, though the latter is partly gestured at.

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 the single slug parameter already documents format, examples, and how to discover valid values. The description adds no additional meaning about the slug, 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 uses a specific verb and resource ("Opt out of a beta feature on your AlterLab account"), which cleanly separates it from the sibling alterlab_enable_beta_feature. It stops just short of a 5 because it never names the counterpart tool or the listing tool as explicit routing alternatives.

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?

It supplies one meaningful exclusion (GA features cannot be disabled) but gives no positive when-to-use framing or pointer to alterlab_list_my_beta_features / alterlab_enable_beta_feature — that pointer exists only in the schema. Usage is inferable from the tool's single, self-evident purpose.

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