Skip to main content
Glama
Cyan Eclipse License Server

Cyan Eclipse License Server

Official

Get the signed revocation list

revocation_list_get
Read-onlyIdempotent

Retrieve a tenant's signed current revocation list of revoked licence IDs, optionally filtered by product, for offline verifiers and auditors. Read-only; requires a tenant ID.

Instructions

Return the tenant's current revocation list: the ids of all revoked licences, optionally filtered to one product, as a body signed with the tenant's current signing key (signature is null when no key store is configured). This is the published artefact offline verifiers and auditors check; under online activation (model B), connected apps instead learn of a revocation at their next check-in, so do not use this as a live status check -- use license_status. Requires a valid _tenant_id. Read-only.

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>"
    },
    "name": "revocation_list_get"
  }
}

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 filter: only revocations for this product.
_principal_idNoActing 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
kidNo
revokedNo
signatureNo
tenant_idNo
product_idNo
generated_atNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds real behavior beyond them: the response is signed with the tenant's current signing key, signature is null when no key store is configured, and the data is a snapshot rather than live state. It does not discuss cost, rate limits, or ordering, which keeps it short of the top mark.

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-loads what is returned, then the artefact's role, then the staleness caveat and the alternative — a sensible order with no filler. It is dense (heavy em-dash use) but each clause carries distinct information; the closing 'Read-only' duplicates annotation coverage.

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 read-only getter with an output schema, full schema coverage, and complete annotations, nothing an agent needs in order to choose and call it correctly is missing. The snapshot semantics and the null-signature edge case are the non-obvious facts, and both are stated.

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 all three parameters are already documented in the input schema, and the description only restates the product filter and the _tenant_id requirement. The principal-gating semantics live entirely in the schema, not the description, so this is a baseline case.

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 ('Return the tenant's current revocation list: the ids of all revoked licences'), adds the optional product filter, and names the signed-body form. It is clearly distinguishable from license_status, which it explicitly points to for live status.

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 an explicit when-not ('do not use this as a live status check') with the replacement named ('use license_status'), and explains the underlying reason (under online activation model B, connected apps learn of revocation at next check-in). The remaining usage context — offline verifiers and auditors — is stated as the intended audience.

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