Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

update_policy

Destructive

Modify a license policy’s name, type, machine or IP limits, and duration so changes apply to every license on that plan, including existing ones.

Instructions

Change a policy (plan/tier): name, type, machine limit, IP limit or duration. This changes every license on the policy, existing ones included, within seconds. 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": {
      "policy": "<policy>"
    },
    "name": "update_policy"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoa new name
typeNoa new type
maxIpsNoa new IP limit; 0 removes it
policyYespolicy id or name
productNoproduct id, code or name, when the policy name exists in several products
maxMachinesNoa new machine limit
durationDaysNoa new duration in days

Output Schema

NameRequiredDescriptionDefault
noteYes
afterYes
beforeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already mark the tool as destructive and non-idempotent, but the description adds the blast radius and timing that annotations cannot convey: the change affects every license on the policy, including existing ones, and propagates "within seconds." That combination (irreversible-feeling propagation plus an explicit user-confirmation instruction) is exactly the behavioral context an agent needs before mutating.

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 short sentences, front-loaded with what changes, followed by the impact and then the required safety step. No filler, and the escalating severity is ordered correctly for an agent reading top-down.

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

Completeness5/5

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

For a 7-parameter mutation tool with a full output schema and complete schema descriptions, the description still carries the parts structured data cannot: scope of propagation, speed of effect, and the user-confirmation requirement. Nothing material for correct invocation is missing.

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%, so every parameter including the maxIps "0 removes it" nuance is already documented in the schema. The description's field list mirrors the schema rather than adding meaning, and it says nothing about the `product` parameter used to disambiguate a policy name across products. 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?

"Change a policy (plan/tier)" gives a specific verb and resource, and the enumerated field list (name, type, machine limit, IP limit, duration) makes clear this is a partial-field update of an existing policy. Against siblings like create_policy, delete_policy and list_policies, the intent is unambiguous without opening a schema.

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?

"Confirm with the user first" is an explicit precondition that tells the agent this is a high-friction, user-approval operation. It doesn't name alternatives or state exclusions (e.g., use create_policy for a new plan, or where access rules should be edited instead), so it falls short of full when/when-not routing.

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