Skip to main content
Glama

Show the license / edition status

license_status
Read-only

Check a deployment's license edition, seat usage, expiry, unlocked features, and rejection status to confirm entitlements or identify Community fallback.

Instructions

Show the deployment's edition and entitlements — Community or a licensed edition, seats used vs allowed, expiry, and unlocked features. If a license was rejected (tampered/expired/wrong key), this says so and reports the Community fallback it's running under.

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": "license_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: it discloses that a rejected license (tampered/expired/wrong key) is surfaced as such, along with the Community fallback actually in effect — telling the agent the output can reflect a degraded/failed state rather than only a success path.

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?

Two sentences, no filler, and the primary content (edition, seats, expiry, features) is front-loaded before the failure-state caveat. Every clause carries distinct information an agent would otherwise have to discover from the output.

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 zero-parameter status tool with an output schema and full annotation coverage, the description supplies everything needed to select and call it: what it reports, the possible degraded states, and the absence of side effects via annotations. Return-value details can safely be left to the output schema.

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?

The tool takes zero parameters and the schema coverage is 100%, so there is no parameter meaning for the description to add. Baseline 4 applies for a parameterless tool.

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 ('Show') plus a precise resource ('deployment's edition and entitlements') and enumerates the contents: Community vs licensed edition, seats used vs allowed, expiry, and unlocked features. An agent can tell this is a licensing/entitlement read, distinct from a general health check, without opening the schema.

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?

Usage is implied rather than stated: the description makes clear it is a status/inspection call, and the mention of 'rejected license' and 'Community fallback' hints at when the agent might care. However, it never explicitly says when to call this versus neighboring status tools such as health or stats, nor does it state any preconditions.

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