Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

block_customer

Destructive

Suspends every active license for a customer so their apps return SUSPENDED until the customer is unblocked; confirm with the user before applying.

Instructions

Block a customer: every active license they hold is suspended (their apps answer SUSPENDED) until unblock_customer. 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": {
      "customer": "<customer>"
    },
    "name": "block_customer"
  }
}

Input Schema

NameRequiredDescriptionDefault
customerYesthe customer's id or email

Output Schema

NameRequiredDescriptionDefault
customerYesthe customer after the change

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Goes beyond the destructiveHint annotation by disclosing the actual blast radius (all active licenses suspended, apps return SUSPENDED) and that it is reversible via unblock_customer. It leaves open how already-expired or already-suspended licenses are treated, and does not clarify whether a repeat call is a no-op despite idempotentHint=false.

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 tight sentences: the effect comes first, the reversal second, the safety instruction last. Every clause earns its place with no repetition of the title or schema.

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 destructive, non-idempotent one-parameter mutation, the description covers the effect, the user-visible symptom, the reversal, and the confirmation requirement; the output schema covers return values. Minor gaps remain around repeat invocation and how non-active licenses are handled.

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% and the single 'customer' parameter already documents id-or-email, so the description adds no format, resolution, or ambiguity-handling detail beyond the schema. Baseline 3 is appropriate when the schema carries the parameter semantics.

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?

Names a specific verb and resource ('Block a customer') and immediately states the concrete effect on their active licenses, which distinguishes it from sibling mutations like delete_customer or deactivate_machine.

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?

Gives a clear operating condition ('Confirm with the user first') and names the reversal path via unblock_customer, so the agent knows the block is meant to be temporary. It does not explicitly contrast with delete_customer or merge_customers, which would have made routing unambiguous.

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