Skip to main content
Glama
Cyan Eclipse License Server

Cyan Eclipse License Server

Official

Reclaim stale activation seats

activation_reclaim_stale
DestructiveIdempotent

Reclaim seats held by stale activations older than the policy reclaim window, optionally scoped to one product, and return the reclaimed activation IDs and count.

Instructions

Reclaim seats held by stale activations: every live activation in the tenant whose last check-in is older than the reclaim window (30 days by policy default) is marked reclaimed, with a seat_reclaim journal receipt per slot. Optionally scoped to one product. Caller must be tenant_owner or issuer AND hold a live mandate covering the reclaim operation class. Fresh activations are untouched, and running it again reclaims nothing further. Returns the reclaimed activation ids and their count.

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

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.
product_idNoOptional: reclaim only within this product.
_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.

Output Schema

NameRequiredDescriptionDefault
countNo
reclaimedNo

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 destructiveHint=true and idempotentHint=true, and the description goes further by naming the exact effect (activations marked reclaimed, seats freed), the audit side effect (a seat_reclaim journal receipt per slot), and the authorization gate (tenant_owner or issuer plus a live mandate covering the reclaim operation class). It also explains the idempotency in concrete terms rather than just repeating the hint.

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?

Structure is strong: core action first, then scope, then authorization, then safety and return values, and every clause carries real information. The opening sentence is dense with parenthetical detail, which costs a little readability but does not waste words.

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, tenant-wide sweep this covers everything an agent needs: blast radius, authorization prerequisites, scope limit, idempotency behavior, and audit artifact. An output schema exists, and the description still summarizes the return (reclaimed ids and count) without over-explaining it.

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% and already explains all three parameters, including that product_id narrows the reclaim scope and that _principal_id is subject to principal/mandate gating. The description restates product scoping and the mandate requirement without adding syntax, defaults, or edge-case meaning the schema lacks, so it lands at the baseline for a fully documented schema.

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?

The description names a specific verb and resource — reclaim seats held by stale activations — plus the exact qualifying condition (last check-in older than the reclaim window, 30 days by default). That distinguishes it cleanly from sibling mutations like activation_deactivate, which act on a named activation rather than sweeping a tenant.

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?

It states when the tool applies (stale check-ins beyond the reclaim window) and gives the boundary conditions that matter: fresh activations are untouched and re-running reclaims nothing further. It does not explicitly name sibling alternatives such as activation_deactivate for a single targeted seat, so the when-not guidance is implied rather than spelled out.

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