Skip to main content
Glama
Cyan Eclipse License Server

Cyan Eclipse License Server

Official

Renew a licence (execute proposal)

license_renew
Destructive

Execute a confirmed renewal proposal to mint a successor licence with renewed terms, link it to the previous licence, and mark that licence superseded.

Instructions

Execute a renew proposal: mint a successor licence carrying the renewed terms, linked to the previous licence, which is marked superseded. Requires the proposal_id, the confirm token bound to its hash (confirm-renew-...), and a live mandate covering the product and the renew operation class. Issuance is journalled before the new 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_renew"
  }
}

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
payloadNo
receiptNo
artefactNo
license_idNo
artefact_hashNo

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 declare destructive=true and idempotent=false, and the description adds substantive context beyond them: the previous licence is marked superseded, a live mandate is required, issuance is journalled before the artefact is returned, and execution is exactly-once. That covers side effects, authorization, audit trail, and retry semantics.

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 and its effect, then prerequisites, then return, then the exactly-once caveat — a logical order with no filler. The return-value enumeration is slightly redundant given an output schema exists, which keeps it just under top marks.

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?

This is a destructive, non-idempotent mint operation, and the description covers authorization prerequisites, what happens to the superseded artefact, the audit journal, and the terminal strongly-typed result. With annotations and an output schema already present, 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.

Parameters3/5

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

Schema coverage is 100% and the schema already documents tenant scoping, proposal state, principal class, and the confirm-token shape. The description largely restates those requirements rather than adding new meaning such as token formatting edge cases or how a stale proposal id is handled. Baseline 3 is appropriate when the schema carries the parameter burden.

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 renew proposal: mint a successor licence carrying the renewed terms') and distinguishes the execution step from the propose step by naming 'the matching propose tool' and the 'propose -> confirm flow'. An agent can tell this apart from license_renew_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?

Prerequisites are spelled out clearly: a proposal still in proposed state, the bound confirm token, and a live mandate covering the product and renew operation class. The 'executes exactly once' clause tells the agent a repeat call is pointless, which is real when-not guidance. It stops short of naming the sibling propose tool explicitly as the required first step.

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