alterlab-mcp-server

Enable Beta Feature

alterlab_enable_beta_feature

Idempotent

Opt in to a beta feature on your AlterLab account by slug to enable experimental capabilities before general release.

Instructions

Opt in to a beta feature on your AlterLab account. Beta features are experimental capabilities available before general release. This operation is idempotent — calling it when already opted in returns success. Use alterlab_list_beta_features to discover available feature slugs.

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_enable_beta_feature"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	URL-safe slug of the beta feature to opt in to (e.g., 'v2-extraction', 'stealth-v3'). Use alterlab_list_beta_features to see available slugs.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.5.0Jun 12, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety and idempotency profile is largely covered. The description adds a small amount of value by spelling out the idempotent behavior ("calling it when already opted in returns success"), but says nothing about permissions, side effects on billing or usage, or what the response contains beyond a success signal.

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?

Four short sentences with the primary action front-loaded and no filler. The idempotency sentence partially restates structured annotation data, but it earns its place by clarifying the success-on-repeat behavior rather than just flagging it.

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 complete annotations, the definition covers purpose, discovery of valid input, and repeat-call behavior. The remaining gap is that no output schema exists and the description does not describe the returned payload beyond implying success.

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%, so the single slug parameter is already fully documented including examples. The description only repeats the pointer to alterlab_list_beta_features, which the schema already states, so it adds no meaning beyond the schema; baseline 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?

"Opt in to a beta feature on your AlterLab account" gives a specific verb (opt in) and resource (beta feature), and the second sentence clarifies what a beta feature is. It does not explicitly name the inverse sibling alterlab_disable_beta_feature, but the opt-in framing plus the tool name makes the enable/disable split unambiguous.

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

Usage Guidelines4/5

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

It tells the agent when to use it (to opt in to experimental capabilities before general release) and routes the agent to alterlab_list_beta_features to obtain valid slugs. It does not state exclusions, prerequisites, or account-eligibility conditions, which is the only missing piece.

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