Skip to main content
Glama

Convert HTML/CSS to JavaFX CSS

html_css_to_javafx_css
Read-onlyIdempotent

Convert HTML/CSS declarations into valid JavaFX CSS and identify unsupported properties, helping you adapt web styles for JavaFX applications.

Instructions

Translate HTML/CSS declarations into valid JavaFX CSS and report unsupported properties.

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

Input Schema

NameRequiredDescriptionDefault
cssNoCSS to convert to JavaFX CSS
htmlNoOptional HTML source; its <style> blocks are used when css is empty

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds one meaningful behavioral fact — unsupported properties are reported rather than silently dropped — but says nothing about how invalid or unparsable CSS is handled, or whether conversion is best-effort.

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 sentence with zero padding, front-loaded with the core transformation before the secondary reporting behavior. Every clause earns its place.

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?

For a two-optional-parameter, fully-annotated, no-output-schema tool, the definition covers purpose and one return characteristic. It falls short only on edge cases an agent may hit — both inputs empty, or malformed CSS — which the schema does not cover either.

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 both parameters are optional and self-documented, so the baseline is 3. The description adds no parameter-level meaning, notably omitting the precedence rule that html is only consulted when css is empty — that rule lives solely in the schema.

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 (Translate) and a precise resource pair (HTML/CSS declarations → valid JavaFX CSS), plus a secondary output ('report unsupported properties'). No sibling tool in the list performs CSS conversion, so an agent can identify it unambiguously from the name and description alone.

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 is only implied by the name and purpose — there is no explicit 'use this when' statement, no mention of the alternative inputs (raw css string vs html with <style> blocks), and no exclusions. Adequate for a single-purpose converter but leaves the invocation choice to inference.

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