Skip to main content
Glama
Cyan Eclipse License Server

Cyan Eclipse License Server

Official

Deactivate an activation (execute proposal)

activation_deactivate
Destructive

Executes a confirmed deactivation proposal to journal the event, mark the activation deactivated, and free its license seat immediately.

Instructions

Execute a deactivate proposal: journal the deactivation and mark the activation deactivated, freeing its seat immediately. Requires the proposal_id, the confirm token bound to its hash (confirm-deactivate-...), and a live mandate covering the product and the deactivate operation class. The affected install sees LICENSE_DEACTIVATED at its next check-in. Returns the activation id, state LICENSE_DEACTIVATED, and the journal receipt. A proposal executes exactly once.

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": {
      "proposal_id": "<proposal_id>",
      "confirm_token": "<confirm_token>",
      "_tenant_id": "<_tenant_id>",
      "_principal_id": "<_principal_id>"
    },
    "name": "activation_deactivate"
  }
}

Input Schema

NameRequiredDescriptionDefault
_tenant_idYesTenant the call acts for. The tenant must exist; an unknown tenant is refused with state LICENSE_UNKNOWN. Transport authentication is a deployment concern -- this parameter scopes the call, it does not authenticate it.
proposal_idYesProposal id returned by the matching propose tool. The proposal must still be in proposed state and belong to the caller's tenant; anything else is refused and logged.
_principal_idYesActing principal inside the tenant. Principal-gated tools refuse unknown principals and principals of the wrong class; executions (tier T2) additionally require a live, unexpired mandate covering the product and the operation class.
confirm_tokenYesConfirm token bound to the proposal hash, in the shape confirm-<verb>-<proposal_id>-<first 12 of the proposal hash>. A token bound to any other proposal or hash is refused and logged; the token is the human-confirmation step of the propose -> confirm flow and is single-use.

Output Schema

NameRequiredDescriptionDefault
stateNo
receiptNo
activation_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare destructive, non-idempotent, non-readOnly; the description adds real behavior beyond them: the seat is freed immediately, the affected install sees LICENSE_DEACTIVATED at its next check-in, a journal receipt is produced, and the proposal executes exactly once.

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 imperative outcome, followed by requirements and the observable side effect; no filler sentences. It is dense but every clause carries information, with only mild repetition between the requirements sentence and the schema.

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?

For a destructive, mandate-gated execution tool the description covers what changes, what the caller needs, when the effect becomes visible, and the return payload. An output schema exists, so no further return-value detail is required.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds meaning the schema does not: it names the confirm-token prefix shape for this verb (confirm-deactivate-...) and ties proposal_id and the mandate to the propose/confirm flow. It does not explain tenant or principal scoping, which the schema already covers.

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 ('Execute a deactivate proposal: journal the deactivation and mark the activation deactivated') and makes the propose-then-execute distinction clear, so an agent can separate it from activation_deactivate_propose without opening either schema.

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?

Preconditions are spelled out: a proposal still in proposed state, a confirm token bound to its hash, and a live mandate covering the product and the deactivate operation class. It stops short of explicitly saying 'call activation_deactivate_propose first' or naming when not to use this tool, which keeps it below a 5.

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