Skip to main content
Glama
Cyan Eclipse License Server

Cyan Eclipse License Server

Official

Propose deactivating an activation

activation_deactivate_propose

Creates a proposal to deactivate a specific activation, so an authorized tenant owner or issuer can start seat release; the seat frees only after the proposal is executed under a mandate.

Instructions

Create a proposal to deactivate one activation, freeing its seat when executed. The activation must exist -- an unknown id is an error here, unlike the read tools. Caller must be tenant_owner or issuer. The proposal alone frees nothing; activation_deactivate executes it under a mandate. Each call creates a fresh proposal.

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": {
      "activation_id": "<activation_id>",
      "_tenant_id": "<_tenant_id>",
      "_principal_id": "<_principal_id>"
    },
    "name": "activation_deactivate_propose"
  }
}

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.
_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.
activation_idYesActivation to deactivate (required).

Output Schema

NameRequiredDescriptionDefault
kindNo
payloadNo
proposal_idNo
proposal_hashNo
confirm_token_shapeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations mark this non-read-only, non-destructive, non-idempotent, so the description enriches rather than repeats: it discloses the authorization class required, that an unknown id errors here unlike read tools, and that every call mints a fresh proposal. It does not cover what the proposal contains, whether it expires, or how long it stays valid, which keeps it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, no filler, and the core action is front-loaded before the permissions and error details. The closing line about fresh proposals earns its place because it clarifies the non-idempotent behavior.

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 three-parameter propose tool with full schema coverage, annotations, and an output schema, the description supplies exactly what structured fields cannot: authorization requirements, error behavior on bad ids, and the propose/execute split. Nothing an agent needs to call it correctly is missing.

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 the baseline is 3, but the description adds a real constraint beyond 'Activation to deactivate (required)': the id must resolve to an existing activation and an unknown id is refused. It adds nothing extra about _tenant_id/_principal_id beyond the schema, which already explains scoping and mandate gating.

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 ('Create a proposal to deactivate one activation') plus an effect ('freeing its seat when executed'). It explicitly distinguishes itself from the executor sibling activation_deactivate, so an agent can pick the right tool without opening a schema.

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 the selection rule against the alternative: the proposal alone frees nothing, and activation_deactivate executes it under a mandate. It also states the preconditions for calling (activation must exist; caller must be tenant_owner or issuer), leaving little to inference.

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