Skip to main content
Glama
Cyan Eclipse License Server

Cyan Eclipse License Server

Official

Verify a licence artefact

license_verify
Read-onlyIdempotent

Verifies a signed .cetlic licence artefact by parsing the envelope, checking Ed25519 signatures and tenant/product expectations, then reconciling stored revocation state read-only.

Instructions

Verify a signed .cetlic licence artefact string: parse the envelope, check the Ed25519 signature against the issuing tenant's registered public keys, check optional tenant/product expectations, then reconcile with the store (an authentic artefact for an unknown licence reports LICENSE_UNKNOWN; a stored state such as REVOKED overrides the artefact's own validity). Use it when an artefact is in hand; use license_status instead when only a licence id is known. The tenant is resolved from the artefact payload, so caller context is optional. 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": {
      "artefact": "<artefact>"
    },
    "name": "license_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
artefactYesThe complete .cetlic artefact string (base64url payload + '.' + base64url signature), exactly as issued.
_tenant_idNoTenant 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: refuse unless the artefact's product_id equals this value.
_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.
expected_tenantNoOptional: refuse unless the artefact's tenant_id equals this value.

Output Schema

NameRequiredDescriptionDefault
stateNo
payloadNo
license_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered; the description's closing 'Read-only' merely restates it. It does add genuine behavioral context beyond annotations: store reconciliation, LICENSE_UNKNOWN for authentic-but-unknown artefacts, and stored state such as REVOKED overriding artefact validity. It does not cover failure modes like malformed base64url or signature mismatch codes, so it is good but not exhaustive.

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 operation and its pipeline, then routing guidance, then a one-word safety tag. The opening sentence is long with several nested clauses, but each clause carries distinct information and nothing is redundant.

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 five-parameter verification tool with an output schema and full annotation coverage, the description supplies the verification pipeline, the store-reconciliation precedence rule, and the sibling routing rule. Return values need not be explained because an output schema exists.

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; the description earns above baseline by explaining that the tenant is resolved from the artefact payload and that caller context is therefore optional, which clarifies why _tenant_id is not required. It does not add detail on expected_tenant or product_id beyond what the schema already states.

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 ('Verify a signed .cetlic licence artefact string') and enumerates the actual steps: parse envelope, check Ed25519 signature against tenant public keys, check expectations, reconcile with store. It explicitly distinguishes itself from the sibling license_status by input type (artefact vs licence id).

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-to-use rule ('when an artefact is in hand') and names the alternative plus the condition that selects it ('use license_status instead when only a licence id is known'). No inference required.

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