Skip to main content
Glama
Sign In
Beaunifi

Beaunifi

by hussainbiedouh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

minify_css

Compress CSS code for production by removing whitespace and comments to reduce file size and improve performance.

Instructions

Minify CSS 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_css"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesCSS code to minify

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It simply restates the operation without describing the return value, error handling, or whether it is a pure transformation. It adds little beyond what the tool name already implies.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single concise sentence with the action and resource front-loaded, and no wasted words. It is appropriately sized for a simple tool, though slightly sparse in detail.

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?

For a one-parameter utility, the description is mostly adequate but does not explicitly state the return value or provide sibling disambiguation. Since there is no output schema or annotations, a brief note such as 'returns minified CSS string' would make it complete.

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 described as 'CSS code to minify'. The tool description does not add parameter-specific meaning beyond the schema, so 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 specific verb ('Minify') and resource ('CSS code'), and adds a clear purpose ('for production'). It distinguishes from sibling tools like beautify_css (opposite operation), minify_js (different resource), and is_minified (detection rather than transformation).

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' gives some context about when to use the tool, but it does not explicitly mention alternatives or exclusions. No guidance is provided for choosing this over beautify_css or minify_js, leaving usage implied.

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