Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

list_access_rules

Read-onlyIdempotent

List blacklist and exclusion rules with match counts to see which access rules are triggering; filter by rule kind or view both.

Instructions

List blacklist and exclusion rules with how often each matched.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_access_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoonly this kind; both when left out

Output Schema

NameRequiredDescriptionDefault
rulesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare this as read-only, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds behavioral value by disclosing that match counts are included, but it does not discuss ordering, pagination, or the meaning or time window of “how often.”

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?

The definition is a single front-loaded sentence with no filler. It efficiently states the resource and the key added output metric.

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?

This is a simple read-only listing tool with one optional enum parameter, complete schema coverage, annotations, and an output schema. The description is sufficient for correct invocation, though it could have noted the optional kind filter or any ordering behavior.

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 kind parameter is fully described as optionally limiting results to BLACKLIST or EXCLUSION. The description reinforces the two rule categories but does not add syntax or filtering semantics beyond what the schema already provides.

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?

The description gives a specific verb and resource: listing blacklist and exclusion rules. It also adds useful scope by saying results include how often each rule matched, though it does not explicitly differentiate this tool from nearby access-rule siblings such as add_access_rule 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description states what the tool returns but gives no explicit guidance on when to use it instead of alternatives. It does not mention add_access_rule, delete_access_rule, or any other list tool, and there are no exclusions or prerequisites.

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