Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

add_access_rule

Create a blacklist to refuse matching license checks or an exclusion that lets trusted machines or IPs pass without consuming machine slots, scoped to an organization, product, or license.

Instructions

Add a blacklist rule (matching license checks answer BLACKLISTED) or an exclusion (matching checks pass without using machine slots, e.g. the developer's own machine or IP). Applies to the whole organization unless a product or license is given. Counts toward the plan's access-rule limit; country rules need Lite or Standard.

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": {
      "kind": "<kind>",
      "type": "<type>",
      "value": "<value>"
    },
    "name": "add_access_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesBLACKLIST (refuse matching checks with BLACKLISTED) or EXCLUSION (let them through without machine limits, e.g. the developer's own machine)
noteNowhy, for the team
typeYesIP (address or CIDR range), HWID (machine id as the app sends it), COUNTRY (two-letter ISO code, blacklist only) or CUSTOMER (customer id, blacklist only)
valueYesthe address, range, machine id, country code or customer id
licenseNoapply to this license only (id, key, key start or email)
productNoapply to this product only (id, code or name)
ignoreStatusNoexclusions only: also let suspended and expired licenses through
expiresInDaysNostop matching after this many days; never when left out

Output Schema

NameRequiredDescriptionDefault
noteYes
addedYes

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?

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=false), the description adds concrete consequences: BLACKLIST causes checks to return BLACKLISTED, EXCLUSION bypasses machine slot consumption, the rule counts against the plan's access-rule limit, and country rules are gated by plan tier. It does not warn that repeated calls create duplicate rules despite idempotentHint=false, which is the main remaining behavioral gap.

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?

Three dense sentences, front-loaded with the definition of the rule kinds before the scoping and plan-constraint details. No filler or restatement of the title, and each sentence carries distinct 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?

An output schema exists and all eight parameters are documented, so the description only needs to cover the operational framing, which it does: plan limits, tier prerequisites, and default organization-wide scope. The only omission is duplicate-creation behavior for a non-idempotent mutation.

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 description coverage is 100%, so the schema already documents kind, type, value, license, product, ignoreStatus and expiresInDays in detail. The description reinforces kind semantics and the license/product scoping default but adds no syntax or format details beyond the schema, so baseline 3 applies.

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 and resource (add an access rule) and then defines the two rule kinds by their observable effect: blacklisted checks answer BLACKLISTED, exclusions pass without consuming machine slots. Combined with the self-explanatory add/list/delete naming across siblings, an agent can tell exactly what this tool does and how it differs from list_access_rules or delete_access_rule.

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 real selection context: it applies organization-wide unless a product or license parameter narrows it, and country rules require the Lite or Standard plan. It does not explicitly exclude or compare against adjacent tools such as block_customer, so the agent must infer that customer-level blocking is a different path.

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