Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

obfuscation_profiles_list

Read-onlyIdempotent

Lists your organization's saved code-obfuscation profiles so you can reuse them across the dashboard, CLI, and downloads; requires Lite or Standard obfuscation.

Instructions

List the organization's saved code-obfuscation profiles (reused by the dashboard, CLI and downloads). Needs the obfuscation feature (Lite or Standard).

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": "obfuscation_profiles_list"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
profilesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish the safety profile (readOnlyHint, idempotent, non-destructive, non-open-world), so the bar is lower. The description still adds real behavioral context beyond them: the entitlement prerequisite (Lite or Standard feature) and the fact that these profiles are consumed by multiple surfaces, both of which affect whether an agent should call this at all.

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 with the resource statement front-loaded and the entitlement constraint following. The parenthetical about dashboard, CLI and downloads is compact and carries genuine information; nothing is padding.

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?

With an output schema present and no input parameters, return shape and argument detail are not the description's job, and the annotation set covers safety. The description supplies scope and the feature prerequisite, leaving little an agent would need that isn't already structured — only pagination or result-size behavior is unaddressed, and with zero params it likely isn't applicable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no argument semantics to explain and the baseline is 4. The description correctly avoids restating anything the empty schema already implies.

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 names a specific verb and resource: "List the organization's saved code-obfuscation profiles", making the scope (organization-wide) and the object (saved profiles) unambiguous. It does not explicitly differentiate itself from sibling obfuscation_status or other list_* tools, but the resource is distinctive enough for an agent to identify it without opening the schema.

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 context is implied rather than stated: "Needs the obfuscation feature (Lite or Standard)" gives a precondition for calling it, and "reused by the dashboard, CLI and downloads" hints at why the profiles matter. However, it never states when to prefer this tool over a sibling or what to do if the feature is unavailable, so guidance remains inferential.

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