Skip to main content
Glama
Cyan Eclipse License Server

Cyan Eclipse License Server

Official

Inspect one activation

activation_inspect
Read-onlyIdempotent

Inspect a single license activation to view its install details, status, timestamps, stale flag, artefact hash, and related journal receipts.

Instructions

Show one activation in full -- install, status, timestamps, stale flag, artefact hash -- plus the journal receipts that name it. Caller must be a principal of class tenant_owner, issuer, or support_reader; support_reader sees a truncated install id. An unknown activation id returns state LICENSE_UNKNOWN rather than an error. 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": {
      "activation_id": "<activation_id>",
      "_tenant_id": "<_tenant_id>",
      "_principal_id": "<_principal_id>"
    },
    "name": "activation_inspect"
  }
}

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.
_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.
activation_idYesActivation id to inspect.

Output Schema

NameRequiredDescriptionDefault
stateNo
receiptsNo
activationNo
activation_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint false), so the bar is lower, and the description still adds real substance: the principal-class requirement, the support_reader truncation of install id, and the non-obvious behavior that an unknown activation id returns state LICENSE_UNKNOWN instead of raising an error. It only omits pagination/volume expectations for the attached journal receipts.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the operation and its returned fields, then access constraints, then edge-case behavior. Every clause carries information an agent needs; there is no filler or restatement of the name.

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 single-record read with an output schema present, the description need not explain return values, and it covers what structured data does not: authorization classes, a redaction rule for one caller class, and the unknown-id state. Nothing an agent needs in order to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description enriches _principal_id meaningfully by enumerating the accepted principal classes (tenant_owner, issuer, support_reader), which the schema only refers to abstractly as "the wrong class." The activation_id parameter itself is self-evident from the schema, so no further value is needed.

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?

The description opens with a specific verb and resource ("Show one activation in full") and enumerates exactly what is returned: install, status, timestamps, stale flag, artefact hash, plus related journal receipts. That is far more specific than a restated title. It stops short of naming a sibling such as activation_list to contrast the single-record read against a listing call, which keeps it at 4.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Useful gating context is given (allowed principal classes, truncation for support_reader), but there is no explicit when-to-use guidance relative to activation_list or journal_list for the receipts. The intended call condition is implied by the field inventory rather than stated, and no exclusions are drawn.

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