Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

reinstate_license

Idempotent

Restore a suspended software license using its ID, key, key prefix, or customer email; revoked licenses cannot be reinstated.

Instructions

Reinstate a suspended license (revoked ones stay revoked).

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": {
      "license": "<license>"
    },
    "name": "reinstate_license"
  }
}

Input Schema

NameRequiredDescriptionDefault
licenseYesthe license id, key, the start of its key, or the customer's email

Output Schema

NameRequiredDescriptionDefault
licenseYesthe license after the change

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 (not read-only, idempotent, not destructive), and the description adds a genuine behavioral constraint beyond them: only suspended licenses are eligible. It leaves ambiguous whether reinstating a revoked license errors out or silently no-ops, which matters for the calling agent.

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?

One sentence, front-loaded with the action, with the eligibility caveat immediately attached. There is no redundant or filler wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter, non-destructive, idempotent mutation with an output schema and full parameter documentation, the definition covers what is needed to select and call it. The only meaningful omission is the outcome when the target license is revoked.

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?

There is a single parameter and the schema description already covers it fully (license id, key, key prefix, or customer email), so the schema carries the burden. The description adds no resolution or precedence guidance for those alternative identifier forms.

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?

States a specific verb and resource ('reinstate a license') and adds a state precondition ('suspended'), which distinguishes it from siblings like suspend_license and revoke_license. It stops short of naming those siblings explicitly, so the differentiation is implied rather than directed.

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

Usage Guidelines4/5

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

The parenthetical 'revoked ones stay revoked' is an explicit when-not-to-use rule, which is the key gating decision for this operation. It does not say what the agent should do instead for a revoked license (there may be no alternative), leaving that one thread hanging.

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