Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

obfuscation_status

Read-onlyIdempotent

Check an obfuscation task by its id to view status, progress, latest log lines, and output file names once finished. Read-only, changes nothing.

Instructions

Check a code-obfuscation run by its task id: its status, progress, the latest log lines and (once it has succeeded) the output file names. Read-only.

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": {
      "task": "<task>"
    },
    "name": "obfuscation_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYesthe obfuscation task id, from obfuscate_file

Output Schema

NameRequiredDescriptionDefault
logYesthe most recent log lines
doneYes
statusYes
taskIdYes
outputsYesnames of the result files once the run has succeeded
progressYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, and 'Read-only' merely restates that. The genuinely additive part is the disclosure that log lines are 'latest' (a tail, not full history) and that output file names only materialize after success, which is real behavioral context beyond 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?

A single front-loaded sentence listing the returned fields in order of availability, followed by a short safety tag. No redundant or filler wording; each clause contributes.

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 and strong annotations, the description only needs to set purpose and scope, which it does, including the success-conditional output. Minor gap: no hint about expected polling cadence or whether a failed status still returns logs.

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?

Only one parameter and schema description coverage is 100%, so the schema already carries its full meaning. The description adds nothing about the id format, but with a fully documented single required param the baseline of 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 concrete verb ('Check') and resource ('a code-obfuscation run'), then enumerates what the check returns: status, progress, latest log lines, and output file names. The obfuscation-specific framing clearly separates it from generic siblings like integration_status.

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?

The 'by its task id' phrasing and the '(once it has succeeded)' clause make the polling context obvious, and the schema links the id to obfuscate_file. It stops short of explicitly telling the agent to re-invoke until success or naming a non-polling alternative, so there is no when-not guidance.

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