Skip to main content
Glama

css_clear

Remove live CSS: one sheet by name, or all sheets if omitted. Panels styled by several sheets get the remaining sheets' values re-applied right away.

Instructions

Remove live CSS: one sheet by name, or all sheets if omitted. Panels styled by several sheets get the remaining sheets' values re-applied right away.

Caveat: once an inline visibility: collapse has been applied, clearing it does NOT make the panel visible again (Panorama keeps the panel's visible flag false). To hide things you may want back, prefer toggling visibility explicitly (set 'visible' again) via js_eval.

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

Input Schema

NameRequiredDescriptionDefault
uiNoauto
sheetNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the immediate re-application of remaining sheets and a non-obvious side effect (clearing an inline visibility:collapse does not restore the panel's visible flag). It does not cover failure behavior for an unknown sheet name, so it falls short of a 5.

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?

Front-loaded with the core action and mode selection, then a clearly separated caveat. The caveat is longer than strictly necessary but contains genuinely non-obvious information, so it earns its space.

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?

An output schema exists, so return values need no explanation, and the destructive side effect is disclosed. The only real gap is the undocumented 'ui' parameter, which matters for a tool with no annotations and no schema descriptions.

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 coverage is 0%, so the description must compensate. It explains the 'sheet' parameter well (name vs. omitted meaning all sheets), but the 'ui' parameter (default 'auto') is never mentioned, leaving half the parameters undocumented.

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 and resource ('Remove live CSS') plus the two operating modes (one sheet by name, or all sheets if omitted), which cleanly separates it from the inverse sibling css_apply.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly covers the when-to-use case and names an alternative path: for things that may need to be shown again, it directs the agent to toggle visibility via js_eval instead. That is a concrete when-not-to-use rule with a named alternative.

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