Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

suspend_license

Destructive

Temporarily suspend a license so the customer's app responds SUSPENDED until reinstated; confirm with the user first.

Instructions

Suspend a license: the customer's app answers SUSPENDED until it is reinstated. Confirm with the user first.

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": "suspend_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

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so safety basics are covered. The description adds real value beyond them by describing the customer-visible outcome (app answers SUSPENDED) and by confirming reversibility via reinstatement, plus an explicit user-confirmation step. It stops short of covering permissions, propagation timing, or side effects on machines.

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 short sentences: the effect comes first, then the confirmation requirement. No redundant restatement of the title and no padding; every clause carries information.

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 one-parameter state-change tool with a full annotations block and an output schema, the description covers effect, reversibility, and pre-call confirmation, which is nearly everything an agent needs. Missing only the operational details (permissions required, whether existing machine activations are affected).

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 with 100% schema description coverage, and the schema already explains that the license may be identified by id, key, key prefix, or customer email. The description adds nothing about the identifier, so this sits at the baseline for a fully documented small schema.

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 gives a specific verb (suspend) and resource (license) and states the concrete effect: the customer's app answers SUSPENDED. That effect, plus the phrase 'until it is reinstated', implicitly separates it from delete_license and revoke_license, but no sibling is named explicitly.

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?

There is one clear guardrail, 'Confirm with the user first', which tells the agent this is a disruptive action needing confirmation. However, it never says when to choose suspend over delete_license, revoke_license, or block_customer, so the agent must infer the distinction from the described effect. That is usable but implied rather than stated.

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