Skip to main content
Glama
Cyan Eclipse License Server

Cyan Eclipse License Server

Official

Revoke a licence (execute proposal)

license_revoke
Destructive

Revokes a licence permanently by journaling the proposal's reason and marking it revoked; requires a valid proposal, confirm token, and live mandate.

Instructions

Execute a revoke proposal: journal the revocation (with the proposal's reason) and mark the licence revoked. Requires the proposal_id, the confirm token bound to its hash (confirm-revoke-...), and a live mandate covering the product and the revoke operation class. Revocation is final -- there is no un-revoke and licence deletion does not exist. Connected clients see LICENSE_REVOKED at their next check-in and the licence joins the signed revocation list. Returns the licence id, state LICENSE_REVOKED, and the journal receipt.

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": "license_revoke"
  }
}

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
license_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag destructive=true and idempotent=false, and the description goes well beyond them: revocation is final with no un-revoke and no licence deletion, the revocation is journaled with the proposal's reason, connected clients observe LICENSE_REVOKED at next check-in, and the licence joins the signed revocation list. It also discloses the authorization burden (live mandate over product and operation class) that annotations cannot express.

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 action, then preconditions, then consequences, then return shape -- a logical order with no filler. It is dense and slightly long for a single call, but every clause carries distinct information.

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?

Complete for a destructive execution tool: irreversibility, downstream effects, authorization requirements and preconditions are all covered, and an output schema exists so return values need no further explanation despite the description summarizing them.

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 coverage is 100%, so proposal_id, confirm_token, _tenant_id and _principal_id are already fully documented. The description restates the mandate requirement and token shape without adding format or syntax detail beyond the schema, so the baseline 3 applies.

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 revoke proposal... mark the licence revoked') and implicitly distinguishes itself from license_revoke_propose by framing this as the execution step of the propose/confirm flow. An agent can tell it apart from the propose sibling 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?

Makes the preconditions explicit -- a proposal still in proposed state, a confirm token bound to its hash, and a live mandate covering the product and revoke operation class -- which tells the agent when this call will succeed. It never names license_revoke_propose as the upstream alternative, so routing is inferred from 'Execute a revoke proposal' rather than stated.

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