developer-tools Static interface comparison
Ignite UI Theming MCP Server
30.0.0 30.1.0
15 schema changes require review.No new authority detected.
View the upgrade review as Markdown
A shareable summary of this comparison for an issue, pull request or ticket. Select the text and copy it.
INTERFACE DIFF
What changed, tool by tool
- 0Added tools
- 0Removed tools
- 15Modified tools
- 15Input-schema changes
- 0Output-schema changes
- 0Declared authority changes
15 tools with recorded changes
create_component_themeModifiedWhat changed
- create_component_theme — Schema change: input property tokens changed: +propertyNames={"type":"string"}.
- create_component_theme — Schema change: input schema keywords changed: -additionalProperties.
Why it could matter
- Calls or consumers built for the earlier schema may need to change.
What to verify
- Validate representative existing tool calls against the new argument schema.
- Declared effect
- unknown → unknown
Input schema
Property Previous (30.0.0) Current (30.1.0) Change (schema root)object, additionalProperties=false object - Constraint: additionalProperties
additionalProperties: false → —tokensobject, additionalProperties {…}required object, additionalProperties {…}, propertyNames {…}required - Changed: propertyNames
propertyNames: — → {"type":"string"}8 unchanged entries
componentdesignSystemlicensednameoutputplatformselectorvariant
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
create_custom_paletteModifiedWhat changed
- create_custom_palette — Schema change: input property error changed: -$ref, +anyOf=[{"properties":{"ba….
- create_custom_palette — Schema change: input property gray changed: anyOf [{"$ref":"#/propert… → [{"properties":{"ba….
- create_custom_palette — Schema change: input property info changed: anyOf [{"$ref":"#/propert… → [{"properties":{"ba….
- create_custom_palette — Schema change: input property primary changed: anyOf [{"additionalProper… → [{"properties":{"ba….
- create_custom_palette — Schema change: input property secondary changed: anyOf [{"$ref":"#/propert… → [{"properties":{"ba….
- create_custom_palette — Schema change: input property success changed: -$ref, +anyOf=[{"properties":{"ba….
- create_custom_palette — Schema change: input property surface changed: anyOf [{"$ref":"#/propert… → [{"properties":{"ba….
- create_custom_palette — Schema change: input property warn changed: -$ref, +anyOf=[{"properties":{"ba….
- create_custom_palette — Schema change: input schema keywords changed: -additionalProperties.
Why it could matter
- Calls or consumers built for the earlier schema may need to change.
What to verify
- Validate representative existing tool calls against the new argument schema.
- Declared effect
- unknown → unknown
Input schema
Property Previous (30.0.0) Current (30.1.0) Change (schema root)object, additionalProperties=false object - Constraint: additionalProperties
additionalProperties: false → —error$ref="#/properties/info"optional anyOf (2)optional - Changed: $ref
- Changed: anyOf
$ref: "#/properties/info" → —anyOf: — → [{"properties":{"baseColor":{"description":"Base color for automatic shade generation using shades() function. Pass the brand color as-is; its lightness does not need adjusting. Valid CSS color formats: hex (\"#3F51B5\", \"#3F51B5AA\"), rgb… (truncated: full value in the exact JSON)grayanyOf (2)optional anyOf (2)optional - Changed: anyOf
anyOf: [{"$ref":"#/properties/primary/anyOf/0"},{"additionalProperties":false,"properties":{"contrastOverrides":{"additionalProperties":{"$ref":"#/properties/primary/anyOf/1/properties/shades/properties/50"},"description":"USUALLY OMIT THIS FIELD.… → [{"properties":{"baseColor":{"description":"Base color for automatic shade generation using shades() function. Pass the brand color as-is; its lightness does not need adjusting. Valid CSS color formats: hex (\"#3F51B5\", \"#3F51B5AA\"), rgb… (truncated: full value in the exact JSON)infoanyOf (2)optional anyOf (2)optional - Changed: anyOf
anyOf: [{"$ref":"#/properties/primary/anyOf/0"},{"$ref":"#/properties/primary/anyOf/1"}] → [{"properties":{"baseColor":{"description":"Base color for automatic shade generation using shades() function. Pass the brand color as-is; its lightness does not need adjusting. Valid CSS color formats: hex (\"#3F51B5\", \"#3F51B5AA\"), rgb… (truncated: full value in the exact JSON)primaryanyOf (2)required anyOf (2)required - Changed: anyOf
anyOf: [{"additionalProperties":false,"properties":{"baseColor":{"description":"Base color for automatic shade generation using shades() function. Pass the brand color as-is; its lightness does not need adjusting. Valid CSS color formats: hex (\"#… → [{"properties":{"baseColor":{"description":"Base color for automatic shade generation using shades() function. Pass the brand color as-is; its lightness does not need adjusting. Valid CSS color formats: hex (\"#3F51B5\", \"#3F51B5AA\"), rgb… (truncated: full value in the exact JSON)secondaryanyOf (2)required anyOf (2)required - Changed: anyOf
anyOf: [{"$ref":"#/properties/primary/anyOf/0"},{"$ref":"#/properties/primary/anyOf/1"}] → [{"properties":{"baseColor":{"description":"Base color for automatic shade generation using shades() function. Pass the brand color as-is; its lightness does not need adjusting. Valid CSS color formats: hex (\"#3F51B5\", \"#3F51B5AA\"), rgb… (truncated: full value in the exact JSON)success$ref="#/properties/info"optional anyOf (2)optional - Changed: $ref
- Changed: anyOf
$ref: "#/properties/info" → —anyOf: — → [{"properties":{"baseColor":{"description":"Base color for automatic shade generation using shades() function. Pass the brand color as-is; its lightness does not need adjusting. Valid CSS color formats: hex (\"#3F51B5\", \"#3F51B5AA\"), rgb… (truncated: full value in the exact JSON)surfaceanyOf (2)required anyOf (2)required - Changed: anyOf
anyOf: [{"$ref":"#/properties/primary/anyOf/0"},{"additionalProperties":false,"properties":{"contrastOverrides":{"additionalProperties":{"$ref":"#/properties/primary/anyOf/1/properties/shades/properties/50"},"description":"USUALLY OMIT THIS FIELD.… → [{"properties":{"baseColor":{"description":"Base color for automatic shade generation using shades() function. Pass the brand color as-is; its lightness does not need adjusting. Valid CSS color formats: hex (\"#3F51B5\", \"#3F51B5AA\"), rgb… (truncated: full value in the exact JSON)warn$ref="#/properties/info"optional anyOf (2)optional - Changed: $ref
- Changed: anyOf
$ref: "#/properties/info" → —anyOf: — → [{"properties":{"baseColor":{"description":"Base color for automatic shade generation using shades() function. Pass the brand color as-is; its lightness does not need adjusting. Valid CSS color formats: hex (\"#3F51B5\", \"#3F51B5AA\"), rgb… (truncated: full value in the exact JSON)6 unchanged entries
designSystemlicensednameoutputplatformvariant
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
create_elevationsModifiedWhat changed
- create_elevations — Schema change: input schema keywords changed: -additionalProperties.
Why it could matter
- Calls or consumers built for the earlier schema may need to change.
What to verify
- Validate representative existing tool calls against the new argument schema.
- Declared effect
- unknown → unknown
Input schema
Property Previous (30.0.0) Current (30.1.0) Change (schema root)object, additionalProperties=false object - Constraint: additionalProperties
additionalProperties: false → —5 unchanged entries
designSystemlicensednameoutputplatform
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
create_paletteModifiedWhat changed
- create_palette — Schema change: input property error changed: -$ref, +pattern="^(#[0-9a-fA-F]{3,4…, +type="string".
- create_palette — Schema change: input property info changed: -$ref, +pattern="^(#[0-9a-fA-F]{3,4…, +type="string".
- create_palette — Schema change: input property scales changed: anyOf [{"anyOf":[{"type":… → [{"anyOf":[{"type":….
- create_palette — Schema change: input property success changed: -$ref, +pattern="^(#[0-9a-fA-F]{3,4…, +type="string".
- create_palette — Schema change: input property warn changed: -$ref, +pattern="^(#[0-9a-fA-F]{3,4…, +type="string".
- create_palette — Schema change: input schema keywords changed: -additionalProperties.
Why it could matter
- Calls or consumers built for the earlier schema may need to change.
What to verify
- Validate representative existing tool calls against the new argument schema.
- Declared effect
- unknown → unknown
Input schema
Property Previous (30.0.0) Current (30.1.0) Change (schema root)object, additionalProperties=false object - Constraint: additionalProperties
additionalProperties: false → —error$ref="#/properties/gray"optional string, pattern="^(#[0-9a-fA-F]{3,4}|#[0-9a-fA-F]{6}|#[0-9a-fA-F]{8}|rgba?\\(.+\\)|hsla?\\(.+\\)|hwb\\(.+\\)|lab\\(.+\\)|lch\\(.+\\)|oklab\\(.+\\)|oklch\\(.+\\)|color\\(.+\\)|[a-z]+)$"optional - Changed: $ref
- Constraint: pattern
- Type changed
$ref: "#/properties/gray" → —pattern: — → "^(#[0-9a-fA-F]{3,4}|#[0-9a-fA-F]{6}|#[0-9a-fA-F]{8}|rgba?\\(.+\\)|hsla?\\(.+\\)|hwb\\(.+\\)|lab\\(.+\\)|lch\\(.+\\)|oklab\\(.+\\)|oklch\\(.+\\)|color\\(.+\\)|[a-z]+)$"type: — → "string"info$ref="#/properties/gray"optional string, pattern="^(#[0-9a-fA-F]{3,4}|#[0-9a-fA-F]{6}|#[0-9a-fA-F]{8}|rgba?\\(.+\\)|hsla?\\(.+\\)|hwb\\(.+\\)|lab\\(.+\\)|lch\\(.+\\)|oklab\\(.+\\)|oklch\\(.+\\)|color\\(.+\\)|[a-z]+)$"optional - Changed: $ref
- Constraint: pattern
- Type changed
$ref: "#/properties/gray" → —pattern: — → "^(#[0-9a-fA-F]{3,4}|#[0-9a-fA-F]{6}|#[0-9a-fA-F]{8}|rgba?\\(.+\\)|hsla?\\(.+\\)|hwb\\(.+\\)|lab\\(.+\\)|lch\\(.+\\)|oklab\\(.+\\)|oklch\\(.+\\)|color\\(.+\\)|[a-z]+)$"type: — → "string"scalesanyOf (2)optional anyOf (2)optional - Changed: anyOf
anyOf: [{"anyOf":[{"type":"string"},{"additionalProperties":false,"properties":{"anchor":{"enum":["surface","white"],"type":"string"},"curve":{"items":{"type":"number"},"maxItems":4,"minItems":4,"type":"array"},"range":{"items":{"type":"number"},"… → [{"anyOf":[{"type":"string"},{"additionalProperties":false,"properties":{"anchor":{"enum":["surface","white"],"type":"string"},"curve":{"items":{"type":"number"},"maxItems":4,"minItems":4,"type":"array"},"range":{"items":{"type":"number"},"… (truncated: full value in the exact JSON)success$ref="#/properties/gray"optional string, pattern="^(#[0-9a-fA-F]{3,4}|#[0-9a-fA-F]{6}|#[0-9a-fA-F]{8}|rgba?\\(.+\\)|hsla?\\(.+\\)|hwb\\(.+\\)|lab\\(.+\\)|lch\\(.+\\)|oklab\\(.+\\)|oklch\\(.+\\)|color\\(.+\\)|[a-z]+)$"optional - Changed: $ref
- Constraint: pattern
- Type changed
$ref: "#/properties/gray" → —pattern: — → "^(#[0-9a-fA-F]{3,4}|#[0-9a-fA-F]{6}|#[0-9a-fA-F]{8}|rgba?\\(.+\\)|hsla?\\(.+\\)|hwb\\(.+\\)|lab\\(.+\\)|lch\\(.+\\)|oklab\\(.+\\)|oklch\\(.+\\)|color\\(.+\\)|[a-z]+)$"type: — → "string"warn$ref="#/properties/gray"optional string, pattern="^(#[0-9a-fA-F]{3,4}|#[0-9a-fA-F]{6}|#[0-9a-fA-F]{8}|rgba?\\(.+\\)|hsla?\\(.+\\)|hwb\\(.+\\)|lab\\(.+\\)|lch\\(.+\\)|oklab\\(.+\\)|oklch\\(.+\\)|color\\(.+\\)|[a-z]+)$"optional - Changed: $ref
- Constraint: pattern
- Type changed
$ref: "#/properties/gray" → —pattern: — → "^(#[0-9a-fA-F]{3,4}|#[0-9a-fA-F]{6}|#[0-9a-fA-F]{8}|rgba?\\(.+\\)|hsla?\\(.+\\)|hwb\\(.+\\)|lab\\(.+\\)|lch\\(.+\\)|oklab\\(.+\\)|oklch\\(.+\\)|color\\(.+\\)|[a-z]+)$"type: — → "string"10 unchanged entries
generatorgraylicensednameoutputplatformprimarysecondarysurfacevariant
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
create_themeModifiedWhat changed
- create_theme — Schema change: input property scales changed: anyOf [{"anyOf":[{"type":… → [{"anyOf":[{"type":….
- create_theme — Schema change: input schema keywords changed: -additionalProperties.
- create_theme: description changed.
Why it could matter
- Calls or consumers built for the earlier schema may need to change.
- Models choose and call tools partly from their descriptions.
What to verify
- Validate representative existing tool calls against the new argument schema.
- Spot-check that agents still select this tool as intended.
- Declared effect
- unknown → unknown
- Description
- PreviousGenerate a complete, production-ready Ignite UI theme with palette, typography, and elevations. <use_case> Use this tool as the starting point for new projects. It generates everything needed for a working theme in a single operation: color palette, typography setup, elevation shadows, and the theme application mixin. </use_case> <workflow> 1. Creates color palette using palette() function 2. Sets up typography with specified font family (if includeTypography: true) 3. Configures elevations based on design system (if includeElevations: true) 4. Configures spacing utilities for Web Components, React, and Blazor (if includeSpacing: true) 5. Applies the theme using the theme() mixin </workflow> <important_notes> REQUIRED COLORS: - primaryColor: Main brand color - secondaryColor: Accent/highlight color - surfaceColor: Background color (should match variant) SHADE PROGRESSION (important): - Primary and secondary colors are NEVER inverted between light/dark themes. - The palette() function generates shades 50=lightest to 900=darkest for ALL chromatic colors regardless of theme variant. - Only gray shades behave differently (for text contrast against surface). - DO NOT provide inverted primary/secondary colors for dark themes. SEED COLORS: - Every shade is solved for a contrast target, so a seed supplies HUE and SATURATION, not lightness - a very light or very dark brand color yields the same ramp as a mid-tone one. Pass the brand color as-is. The one caveat: a seed with very little chroma (a tinted gray such #6c757d) keeps that tint rather than being saturated, so it produces a tinted-gray ramp; a seed with no measurable hue produces a pure gray one. PLATFORM DIFFERENCES: - Angular: Uses igniteui-angular/theming with core() and theme() mixins - Web Components: Uses igniteui-theming directly with palette(), typography(), elevations() mixins - React: Uses igniteui-theming directly (same as Web Components), common with Vite/Next.js - Blazor: Uses igniteui-theming for Sass compilation, theme CSS referenced in Blazor components SASS FILE PLACEMENT: - When combining Sass output from multiple tools into one file, all @use rules must appear at the top before any other statements. Deduplicate @use lines that share the same module path. </important_notes> <output> Returns: - Complete Sass code with all theme components - List of variables created/used - Platform-specific guidance </output> <error_handling> - Invalid color format: Returns error with format examples - Variant mismatch: Warns if surface color doesn't match theme variant </error_handling> <example> Complete Material Design blue theme: { "platform": "angular", "designSystem": "material", "primaryColor": "#1976D2", "secondaryColor": "#FF9800", "surfaceColor": "#FAFAFA", "variant": "light", "fontFamily": "'Roboto', sans-serif", "includeTypography": true, "includeElevations": true } </example> <next_steps> After generating a theme: 1. Import the generated Sass file in your application's main styles 2. Customize individual component themes as needed using component schema overrides </next_steps> <related_tools> - detect_platform: Run first to auto-detect platform from package.json - create_custom_palette: Only when exact per-shade values are mandated by a brand spec - create_palette: Use if you only need a palette without full theme - create_typography: Use if you only need typography setup - create_elevations: Use if you only need elevation shadows </related_tools> <related_resources> Call read_resource to load reference data: - "theming://presets/palettes" — preset palette colors - "theming://guidance/colors" — color guidance overview - "theming://guidance/colors/rules" — light/dark theme color rules - "theming://platforms/angular" — Angular platform configuration - "theming://platforms/webcomponents" — Web Components platform configuration - "theming://platforms/react" — React platform configuration - "theming://platforms/blazor" — Blazor platform configuration </related_resources>
- CurrentGenerate a complete, production-ready Ignite UI theme with palette, typography, and elevations. <use_case> Use this tool as the starting point for new projects. It generates everything needed for a working theme in a single operation: color palette, typography setup, elevation shadows, and the theme application mixin. </use_case> <workflow> 1. Creates color palette using palette() function 2. Sets up typography with specified font family (if includeTypography: true) 3. Configures elevations based on design system (if includeElevations: true) 4. Configures spacing utilities for Web Components, React, and Blazor (if includeSpacing: true) 5. Applies the theme using the theme() mixin For Web Components, React, and Blazor the output always includes sizing(), the progress @property rules, the scrollbar variables and .ig-scrollbar class, RTL support, and the tile manager view transitions. </workflow> <important_notes> REQUIRED COLORS: - primaryColor: Main brand color - secondaryColor: Accent/highlight color - surfaceColor: Background color (should match variant) SHADE PROGRESSION (important): - Primary and secondary colors are NEVER inverted between light/dark themes. - The palette() function generates shades 50=lightest to 900=darkest for ALL chromatic colors regardless of theme variant. - Only gray shades behave differently (for text contrast against surface). - DO NOT provide inverted primary/secondary colors for dark themes. SEED COLORS: - Every shade is solved for a contrast target, so a seed supplies HUE and SATURATION, not lightness - a very light or very dark brand color yields the same ramp as a mid-tone one. Pass the brand color as-is. The one caveat: a seed with very little chroma (a tinted gray such #6c757d) keeps that tint rather than being saturated, so it produces a tinted-gray ramp; a seed with no measurable hue produces a pure gray one. PLATFORM DIFFERENCES: - Angular: Uses igniteui-angular/theming with core() and theme() mixins - Web Components: Uses igniteui-theming directly with palette(), typography(), elevations() mixins - React: Uses igniteui-theming directly (same as Web Components), common with Vite/Next.js - Blazor: Uses igniteui-theming for Sass compilation, theme CSS referenced in Blazor components SASS FILE PLACEMENT: - When combining Sass output from multiple tools into one file, all @use rules must appear at the top before any other statements. Deduplicate @use lines that share the same module path. </important_notes> <output> Returns: - Complete Sass code with all theme components - List of variables created/used - Platform-specific guidance </output> <error_handling> - Invalid color format: Returns error with format examples - Variant mismatch: Warns if surface color doesn't match theme variant </error_handling> <example> Complete Material Design blue theme: { "platform": "angular", "designSystem": "material", "primaryColor": "#1976D2", "secondaryColor": "#FF9800", "surfaceColor": "#FAFAFA", "variant": "light", "fontFamily": "'Roboto', sans-serif", "includeTypography": true, "includeElevations": true } </example> <next_steps> After generating a theme: 1. Import the generated Sass file in your application's main styles 2. Customize individual component themes as needed using component schema overrides </next_steps> <related_tools> - detect_platform: Run first to auto-detect platform from package.json - create_custom_palette: Only when exact per-shade values are mandated by a brand spec - create_palette: Use if you only need a palette without full theme - create_typography: Use if you only need typography setup - create_elevations: Use if you only need elevation shadows </related_tools> <related_resources> Call read_resource to load reference data: - "theming://presets/palettes" — preset palette colors - "theming://guidance/colors" — color guidance overview - "theming://guidance/colors/rules" — light/dark theme color rules - "theming://platforms/angular" — Angular platform configuration - "theming://platforms/webcomponents" — Web Components platform configuration - "theming://platforms/react" — React platform configuration - "theming://platforms/blazor" — Blazor platform configuration </related_resources>
Input schema
Property Previous (30.0.0) Current (30.1.0) Change (schema root)object, additionalProperties=false object - Constraint: additionalProperties
additionalProperties: false → —scalesanyOf (2)optional anyOf (2)optional - Changed: anyOf
anyOf: [{"anyOf":[{"type":"string"},{"additionalProperties":false,"properties":{"anchor":{"enum":["surface","white"],"type":"string"},"curve":{"items":{"type":"number"},"maxItems":4,"minItems":4,"type":"array"},"range":{"items":{"type":"number"},"… → [{"anyOf":[{"type":"string"},{"additionalProperties":false,"properties":{"anchor":{"enum":["surface","white"],"type":"string"},"curve":{"items":{"type":"number"},"maxItems":4,"minItems":4,"type":"array"},"range":{"items":{"type":"number"},"… (truncated: full value in the exact JSON)14 unchanged entries
designSystemfontFamilygeneratorincludeElevationsincludeSpacingincludeTypographylicensednameoutputplatformprimaryColorsecondaryColorsurfaceColorvariant
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
create_typographyModifiedWhat changed
- create_typography — Schema change: input property customScale changed: additionalProperties {"additionalPropert… → {"properties":{"fon…, +propertyNames={"type":"string"}.
- create_typography — Schema change: input schema keywords changed: -additionalProperties.
Why it could matter
- Calls or consumers built for the earlier schema may need to change.
What to verify
- Validate representative existing tool calls against the new argument schema.
- Declared effect
- unknown → unknown
Input schema
Property Previous (30.0.0) Current (30.1.0) Change (schema root)object, additionalProperties=false object - Constraint: additionalProperties
additionalProperties: false → —customScaleobject, additionalProperties {…}optional object, additionalProperties {…}, propertyNames {…}optional - Constraint: additionalProperties
- Changed: propertyNames
additionalProperties: {"additionalProperties":false,"properties":{"fontSize":{"type":"string"},"fontStyle":{"type":"string"},"fontWeight":{"type":["string","number"]},"letterSpacing":{"type":"string"},"lineHeight":{"type":"string"},"marginBottom":{"type":"string… → {"properties":{"fontSize":{"type":"string"},"fontStyle":{"type":"string"},"fontWeight":{"type":["string","number"]},"letterSpacing":{"type":"string"},"lineHeight":{"type":"string"},"marginBottom":{"type":"string"},"marginTop":{"type":"strin… (truncated: full value in the exact JSON)propertyNames: — → {"type":"string"}6 unchanged entries
designSystemfontFamilylicensednameoutputplatform
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
detect_platformModifiedWhat changed
- detect_platform — Schema change: input schema keywords changed: -additionalProperties.
Why it could matter
- Calls or consumers built for the earlier schema may need to change.
What to verify
- Validate representative existing tool calls against the new argument schema.
- Declared effect
- unknown → unknown
Input schema
Property Previous (30.0.0) Current (30.1.0) Change (schema root)object, additionalProperties=false object - Constraint: additionalProperties
additionalProperties: false → —1 unchanged entry
packageJsonPath
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
fit_color_scaleModifiedWhat changed
- fit_color_scale — Schema change: input property added: family.
- fit_color_scale — Schema change: input property name changed: description "Optional label for… → "Optional label for….
- fit_color_scale — Schema change: input schema keywords changed: -additionalProperties.
- fit_color_scale: description changed.
Why it could matter
- Calls or consumers built for the earlier schema may need to change.
- Models choose and call tools partly from their descriptions.
What to verify
- Validate representative existing tool calls against the new argument schema.
- Spot-check that agents still select this tool as intended.
- Declared effect
- unknown → unknown
- Description
- PreviousDerive a shade scale from an existing color ladder. <use_case> Use when shades must follow the rhythm of a ladder you already have - another design system's grays, a brand ramp, a palette from a screenshot. Pass the returned spec to create_palette or create_theme as `scales`. Never hand-write range/curve values. Not needed for the built-in presets ("even" | "material" | "tailwind" | "carbon") - name those in `scales` directly. </use_case> <important_notes> - Order the colors LIGHTEST FIRST (a 50-900 ladder already is). 3 minimum, 10 fits best. - The response reports how closely the fit reproduces the ladder; a ladder that does not follow one smooth curve fits loosely and says so. - A scale sets rhythm only, never hue - the seed still decides the color. - Background: read_resource "igniteui-theming://guidance/colors/scales" </important_notes> <example> { "colors": ["#f8fafc","#f1f5f9","#e2e8f0","#cbd5e1","#94a3b8", "#64748b","#475569","#334155","#1e293b","#0f172a"], "name": "gray" } </example>
- CurrentDerive a shade scale from an existing color ladder. <use_case> Use when shades must follow the rhythm of a ladder you already have - another design system's grays, a brand ramp, a palette from a screenshot. Pass the returned spec to create_palette or create_theme as `scales`. Never hand-write range/curve values. Not needed for the built-in presets ("even" | "material" | "tailwind" | "carbon") - name those in `scales` directly. </use_case> <important_notes> - Order the colors LIGHTEST FIRST (a 50-900 ladder already is). 3 minimum, 10 fits best. - The response reports how closely the fit reproduces the ladder; a ladder that does not follow one smooth curve fits loosely and says so. - A scale sets rhythm only, never hue - the seed still decides the color. - Set `family` to the palette family the ladder is for; it keys the returned scales map. `name` is only a label. - Background: read_resource "theming://guidance/colors/scales" </important_notes> <example> { "colors": ["#f8fafc","#f1f5f9","#e2e8f0","#cbd5e1","#94a3b8", "#64748b","#475569","#334155","#1e293b","#0f172a"], "family": "gray", "name": "Tailwind slate" } </example>
Input schema
Property Previous (30.0.0) Current (30.1.0) Change (schema root)object, additionalProperties=false object - Constraint: additionalProperties
additionalProperties: false → —familynot present string, enum (7)optional - Added
namestringoptional stringoptional - Description changed
2 unchanged entries
colorscolors › [items]
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
get_chart_series_colorsModifiedWhat changed
- get_chart_series_colors — Schema change: input schema keywords changed: -additionalProperties.
Why it could matter
- Calls or consumers built for the earlier schema may need to change.
What to verify
- Validate representative existing tool calls against the new argument schema.
- Declared effect
- unknown → unknown
Input schema
Property Previous (30.0.0) Current (30.1.0) Change (schema root)object, additionalProperties=false object - Constraint: additionalProperties
additionalProperties: false → —5 unchanged entries
chartTypecustomBrushescustomBrushes › [items]indexmode
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
get_colorModifiedWhat changed
- get_color — Schema change: input schema keywords changed: -additionalProperties.
Why it could matter
- Calls or consumers built for the earlier schema may need to change.
What to verify
- Validate representative existing tool calls against the new argument schema.
- Declared effect
- unknown → unknown
Input schema
Property Previous (30.0.0) Current (30.1.0) Change (schema root)object, additionalProperties=false object - Constraint: additionalProperties
additionalProperties: false → —4 unchanged entries
colorcontrastopacityvariant
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
get_component_design_tokensModifiedWhat changed
- get_component_design_tokens — Schema change: input schema keywords changed: -additionalProperties.
Why it could matter
- Calls or consumers built for the earlier schema may need to change.
What to verify
- Validate representative existing tool calls against the new argument schema.
- Declared effect
- unknown → unknown
Input schema
Property Previous (30.0.0) Current (30.1.0) Change (schema root)object, additionalProperties=false object - Constraint: additionalProperties
additionalProperties: false → —1 unchanged entry
component
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
read_resourceModifiedWhat changed
- read_resource — Schema change: input schema keywords changed: -additionalProperties.
Why it could matter
- Calls or consumers built for the earlier schema may need to change.
What to verify
- Validate representative existing tool calls against the new argument schema.
- Declared effect
- unknown → unknown
Input schema
Property Previous (30.0.0) Current (30.1.0) Change (schema root)object, additionalProperties=false object - Constraint: additionalProperties
additionalProperties: false → —1 unchanged entry
uri
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
set_roundnessModifiedWhat changed
- set_roundness — Schema change: input schema keywords changed: -additionalProperties.
Why it could matter
- Calls or consumers built for the earlier schema may need to change.
What to verify
- Validate representative existing tool calls against the new argument schema.
- Declared effect
- unknown → unknown
Input schema
Property Previous (30.0.0) Current (30.1.0) Change (schema root)object, additionalProperties=false object - Constraint: additionalProperties
additionalProperties: false → —5 unchanged entries
componentoutputplatformradiusFactorscope
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
set_sizeModifiedWhat changed
- set_size — Schema change: input schema keywords changed: -additionalProperties.
Why it could matter
- Calls or consumers built for the earlier schema may need to change.
What to verify
- Validate representative existing tool calls against the new argument schema.
- Declared effect
- unknown → unknown
Input schema
Property Previous (30.0.0) Current (30.1.0) Change (schema root)object, additionalProperties=false object - Constraint: additionalProperties
additionalProperties: false → —5 unchanged entries
componentoutputplatformscopesize
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
set_spacingModifiedWhat changed
- set_spacing — Schema change: input schema keywords changed: -additionalProperties.
Why it could matter
- Calls or consumers built for the earlier schema may need to change.
What to verify
- Validate representative existing tool calls against the new argument schema.
- Declared effect
- unknown → unknown
Input schema
Property Previous (30.0.0) Current (30.1.0) Change (schema root)object, additionalProperties=false object - Constraint: additionalProperties
additionalProperties: false → —7 unchanged entries
blockcomponentinlineoutputplatformscopespacing
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
No tools match these filters.
Evidence and provenance
- Static findings
- REVIEW from Modelara’s automated analysis of the two declared interfaces. A policy outcome, not a security rating or a runtime test.
- Human review
- Pending human review. No reviewer decision is recorded for this comparison.
- Published evidence
- Part of Valyd’s published data generation listed in valyd-data-source.json. Published records are not rewritten.
Show provenance and exact files
- Comparison
igniteui-theming/30.0.0~30.1.0The published comparison identifier.- Analyzer
modelara v0.1.8Policy version not recorded.Analyzed Nov 16, 2026, 9:58 PM UTC.- Distribution
npm- Previous release
igniteui-theming@30.0.015 tools · published by the registry Oct 22, 2026, 10:25 AM UTCArtifact integritysha512-hccCKuxbn1CvQO0IGB1BZn1GvxHyWHcfWEN9CzHreEikeaDPiAi/EUt37h9U2ZJtnwYKU1Bdejajo8stnqUfOQ==Interface fingerprintsha256:9b88d20ab02d368b874d422fff6a8d3a7e67a8ffa4f3d2263c6dd708483a47b9Exact interface snapshot (JSON)- Current release
igniteui-theming@30.1.015 tools · published by the registry Nov 3, 2026, 8:02 AM UTCArtifact integritysha512-3UEK2p4Aw5fu9v0MNlyqauapx99oBVoPmYp/A3IA71Y3FhKHnfEhnPshwxLR4qHi7XRSpAO84Nekmo4gSH1ZoA==Interface fingerprintsha256:5c8de285c65caa5dffea200b5932c2bcf240c0c59ed3748244229a90f099310eExact interface snapshot (JSON)- Comparison record
- Exact comparison record (JSON)
The integrity value or digest identifies the exact artifact that was inspected; it does not show that the package is safe. The interface fingerprint identifies the declared tools and schemas Modelara recorded for that release.
MODELARA ANALYSIS OUTPUT
Interface findings
Requires review
15 findingscreate_component_themeREVIEWChangedShow details
input property tokens changed: +propertyNames={"type":"string"}input schema keywords changed: -additionalProperties
create_custom_paletteREVIEWChangedShow details
input property error changed: -$ref, +anyOf=[{"properties":{"ba…input property gray changed: anyOf [{"$ref":"#/propert… → [{"properties":{"ba…input property info changed: anyOf [{"$ref":"#/propert… → [{"properties":{"ba…input property primary changed: anyOf [{"additionalProper… → [{"properties":{"ba…input property secondary changed: anyOf [{"$ref":"#/propert… → [{"properties":{"ba…input property success changed: -$ref, +anyOf=[{"properties":{"ba…input property surface changed: anyOf [{"$ref":"#/propert… → [{"properties":{"ba…input property warn changed: -$ref, +anyOf=[{"properties":{"ba…input schema keywords changed: -additionalProperties
create_elevationsREVIEWChangedShow details
input schema keywords changed: -additionalProperties
create_paletteREVIEWChangedShow details
input property error changed: -$ref, +pattern="^(#[0-9a-fA-F]{3,4…, +type="string"input property info changed: -$ref, +pattern="^(#[0-9a-fA-F]{3,4…, +type="string"input property scales changed: anyOf [{"anyOf":[{"type":… → [{"anyOf":[{"type":…input property success changed: -$ref, +pattern="^(#[0-9a-fA-F]{3,4…, +type="string"input property warn changed: -$ref, +pattern="^(#[0-9a-fA-F]{3,4…, +type="string"input schema keywords changed: -additionalProperties
create_themeREVIEWChangedShow details
input property scales changed: anyOf [{"anyOf":[{"type":… → [{"anyOf":[{"type":…input schema keywords changed: -additionalProperties
create_typographyREVIEWChangedShow details
input property customScale changed: additionalProperties {"additionalPropert… → {"properties":{"fon…, +propertyNames={"type":"string"}input schema keywords changed: -additionalProperties
detect_platformREVIEWChangedShow details
input schema keywords changed: -additionalProperties
fit_color_scaleREVIEWChangedShow details
input property added: familyinput property name changed: description "Optional label for… → "Optional label for…input schema keywords changed: -additionalProperties
get_chart_series_colorsREVIEWChangedShow details
input schema keywords changed: -additionalProperties
get_colorREVIEWChangedShow details
input schema keywords changed: -additionalProperties
get_component_design_tokensREVIEWChangedShow details
input schema keywords changed: -additionalProperties
read_resourceREVIEWChangedShow details
input schema keywords changed: -additionalProperties
set_roundnessREVIEWChangedShow details
input schema keywords changed: -additionalProperties
set_sizeREVIEWChangedShow details
input schema keywords changed: -additionalProperties
set_spacingREVIEWChangedShow details
input schema keywords changed: -additionalProperties
Informational
2 findingscreate_themeINFOChangedfit_color_scaleINFOChanged
What do these results mean?
- PASS
- No policy-significant interface change detected.
- REVIEW
- Interface changes require inspection.
- FAIL
- A policy-significant change was detected.
- INVALID
- The comparison could not be evaluated reliably.