Skip to main content
Glama
Cyan Eclipse License Server

Cyan Eclipse License Server

Official

Show server policy and posture

policy_show
Read-onlyIdempotent

Inspect server identity, policy defaults, tier floors, denylist, signing key IDs, and journal head to orient tenant discovery. Read-only; changes nothing.

Instructions

Show this server's identity, policy defaults (heartbeat 4 h, offline window 72 h, seat-reclaim window 30 d, expiry grace 14 d, clock tolerances), the tier floor of every tool, the denylist, the tenant's signing key ids in force, and the tenant's journal head. Use it first, for orientation and discovery; it is the only tool that answers without a valid tenant (an absent or unknown tenant gets the genesis journal head and no key ids). It reports posture, never licence state -- use license_status or license_inspect for a licence. Read-only; changes nothing.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "policy_show"
  }
}

Input Schema

NameRequiredDescriptionDefault
_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.
_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
toolsNo
policyNo
tenantNo
denylistNo
identityNo
tier_floorsNo
journal_headNo
kids_in_forceNo

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 declare readOnly/idempotent/non-destructive, so the repeated 'Read-only; changes nothing' earns nothing. The description does add behavior annotations cannot carry: it is the only tool that answers without a valid tenant, and an absent/unknown tenant yields the genesis journal head with no key ids. It stops short of describing output shape, but an output schema exists.

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 payload contents, then usage, then the licence exclusion — good ordering with no filler sentences. The parenthetical list of default values is dense but each item is substantive; the enumeration could be tighter.

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?

Given a read-only diagnostic tool with full annotation coverage, a fully described 2-parameter schema, and an output schema, the description supplies everything an agent needs: what it returns, when to call it, that it works unauthenticated, and what it does not report.

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 the schema already documents both parameters; baseline 3 applies. The description does touch tenant semantics ('absent or unknown tenant'), but this creates a tension with the schema, which says an unknown tenant is refused with LICENSE_UNKNOWN, whereas the description promises a genesis journal head instead — ambiguity rather than added clarity.

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 opens with a concrete verb and enumerates exactly what 'show' returns (identity, policy defaults with actual values, tier floor, denylist, signing key ids, journal head). It is impossible to confuse with license_status or license_inspect because it explicitly disclaims licence state.

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?

Explicit routing: 'Use it first, for orientation and discovery' establishes call order, and 'use license_status or license_inspect for a licence' names the alternatives and the condition that selects them. The special case (works without a valid tenant) is a genuine when-to-use rule rather than generic filler.

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