Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

unblock_customer

Restore access for a blocked customer by reinstating licenses suspended by the block; manually suspended licenses stay unchanged.

Instructions

Unblock a customer and reinstate the licenses the block suspended (not ones suspended by hand).

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

A3.8/5.0
Behavior4/5

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

Annotations only declare the general write profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the description's disclosure that the call restores licenses suspended by the block is genuinely additive context. It leaves the non-idempotent behavior and the outcome when the customer is already unblocked unexplained.

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?

A single sentence with no filler; the primary action comes first and the important scope caveat is attached immediately after in parentheses.

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?

An output schema exists, so return values need not be described, and the key side effect on licenses is covered. What is missing is the edge-case behavior: a no-op or error when the customer is not blocked, and the reason idempotentHint is false.

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?

Only one parameter and schema description coverage is 100%, with 'the customer's id or email' already documented in the schema. The description adds no further meaning, such as whether email is resolved case-insensitively or errors when ambiguous, so the baseline 3 applies.

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 ('Unblock a customer') and adds a scope qualifier about which licenses are reinstated, which implicitly contrasts with block_customer. It stops short of naming that sibling explicitly or stating what it means for a customer who is not currently blocked.

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 by the name and by the parenthetical exclusion of hand-suspended licenses, but there is no explicit when-to-use statement, no prerequisite (e.g. customer must currently be blocked), and no named alternative for restoring licenses suspended manually or for full removal via delete_customer.

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