Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

delete_access_rule

DestructiveIdempotent

Remove a blacklist or exclusion rule so blocked machines can access again and excluded machines count toward license limits; confirm with the user first.

Instructions

Delete a blacklist or exclusion rule; blocked machines get back in, excluded ones count against limits again. 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": {
      "id": "<id>"
    },
    "name": "delete_access_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe rule's id, from list_access_rules

Output Schema

NameRequiredDescriptionDefault
deletedYesthe id of what was deleted

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=true, so the bar is lower, yet the description adds real semantic consequence: blocked machines regain access and excluded machines count against limits again. The explicit "confirm with the user first" also flags an interaction requirement not present in the annotations.

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, zero filler, with the effect of the deletion front-loaded ahead of the confirmation instruction. Nothing could be removed without losing 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?

A simple single-parameter mutation with an output schema and full annotation coverage; the description covers impact and the confirm-first requirement, which is most of what an agent needs. Minor gaps remain, such as behavior when the id does not exist, but they are not blocking.

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% and the single id parameter already documents its source (list_access_rules). The description adds no format, validation, or sourcing detail beyond the schema, 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?

"Delete a blacklist or exclusion rule" gives a specific verb and resource, and the follow-on clause spells out the two rule categories the tool operates on. It separates this from add_access_rule/list_access_rules by implication of the verb, though it never names a sibling 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?

"Confirm with the user first" gives a procedural precondition for use, which is useful. It does not state when to choose this over alternatives or what happens if the id is wrong, so usage is only partially implied rather than fully guided.

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