Skip to main content
Glama
Sign In
Beaunifi

Beaunifi

by hussainbiedouh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

minify_js

Minify JavaScript code to reduce file size and improve page load performance. Removes unnecessary characters while preserving functionality.

Instructions

Minify JavaScript code for production

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": {
      "code": "<code>"
    },
    "name": "minify_js"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesJavaScript code to minify

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only restates the obvious action (minifying code) and does not mention whether the result is returned as a string, whether invalid JavaScript is rejected, whether comments are stripped, or whether the operation has any side effects.

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 description is a single, front-loaded sentence with no filler words. Every word contributes to the core purpose, making it highly concise and easy to parse.

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

Completeness3/5

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

The tool is simple with one parameter and no output schema, so the description is minimally adequate. However, it would be more complete if it stated that the input is minified and returned as a result, and it does not cover error behavior or constraints. These are clear gaps but not severe for such a straightforward operation.

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 'code' parameter is already documented as 'JavaScript code to minify'. The tool description adds no new meaning beyond the schema, which is acceptable given the high coverage, but it does not enrich the parameter semantics further.

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?

The description clearly states a specific verb ('Minify'), a specific resource ('JavaScript code'), and an intended context ('for production'). It distinguishes itself from siblings like beautify_js (opposite action) and minify_css (different language) without requiring 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?

The phrase 'for production' implies this is for production-ready output, and the resource name clearly indicates JavaScript as opposed to CSS. However, it does not explicitly describe when to choose this over beautify_js, minify_css, or is_minified, nor does it provide any exclusion criteria.

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

Deploy Server

Other Tools