Skip to main content
Glama
Cyan Eclipse License Server

Cyan Eclipse License Server

Official

Supersede or transfer a licence (execute proposal)

license_supersede
Destructive

Executes a renew proposal as a supersede or transfer, minting a successor licence and marking the previous one superseded after confirmation.

Instructions

Execute a renew-kind proposal as a supersede -- or, with transfer true, as a transfer -- minting a successor licence and marking the previous licence superseded. Uses the supersede confirm verb (confirm-supersede-...) even though the proposal kind is renew, and requires a live mandate covering the supersede (or transfer) operation class for the product. Issuance is journalled before the artefact is returned. Returns the new licence id, artefact, hash, payload, and 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": "license_supersede"
  }
}

Input Schema

NameRequiredDescriptionDefault
transferNoTrue executes as a transfer (transfer operation class and journal verb); false (default) as a supersede.
_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
payloadNo
receiptNo
artefactNo
license_idNo
artefact_hashNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that the supersede confirm verb is used despite the renew proposal kind, that a mandate must cover the operation class, that issuance is journalled before the artefact is returned, and that a proposal executes exactly once (reinforcing idempotentHint=false). The destructiveHint=true annotation is corroborated by 'marking the previous licence superseded' rather than contradicted.

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 core action and the transfer variant in the first sentence, followed by prerequisites and the execution guarantee. Dense but nearly every clause carries operational information; the one lower-value sentence is the enumeration of return values, which the output schema already covers.

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, it covers the state requirement, the mandate requirement, the odd confirm-verb convention, journaling order, and the execute-once guarantee, with return values backed by an output schema. An agent has enough to decide and invoke correctly; the only redundancy is restating the return fields.

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 all five parameters are already documented in detail, including the transfer flag's two operation classes and the confirm token's shape. The description only restates the transfer semantics and adds no format, default, or edge-case information beyond the schema, 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?

Specific verb and resource: 'Execute a renew-kind proposal as a supersede ... minting a successor licence and marking the previous licence superseded', plus the transfer variant. It implicitly separates itself from a direct renew by insisting the input is a proposal, but it never names the sibling tools it is not (license_renew, license_renew_propose), so differentiation requires inference from the sibling list.

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?

States clear preconditions: the proposal must be a renew-kind in proposed state, the caller needs a live mandate covering the supersede (or transfer) operation class for the product, and execution happens exactly once. It does not state when an agent should prefer the direct renew path over this proposal-execution path, nor any explicit exclusions, so it stops short of full when/when-not guidance.

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