Filo

List Component Tokens

tokens_list_component_vars

Read-only

List the --bsi- CSS custom properties you can override to customize any Bootstrap Italia component, including semantic description, resolution chain, and resolved value. Override these safe variables instead of central design tokens.

Instructions

Lists the CSS custom properties (--bsi-) you can override in your own CSS to customize a Bootstrap Italia component, each with a semantic description, resolution chain (resolvedVia), and concrete resolved value (e.g. var(--bsi-spacing-m) → 24px). These --bsi- variables are always safe to override at runtime; the central Design Tokens they resolve through (--it-/$it-, visible in resolvedVia) are not meant to be overridden per-project, override the --bsi- variable itself instead.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`component`	Yes	Component name or slug (e.g. "accordion", "Alert")

Output Schema

TableJSON Schema

Name	Required	Description	Default
`meta`	Yes
`total`	Yes
`tokens`	Yes
`summary`	Yes
`component`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed8 schema fields changedv0.5.0Aug 14, 2026

addedOutput schema / properties / meta / properties / designersUrl
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / summary / properties / ambiguous
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / summary / properties / composite
```
Added value: +{
+  "type": "number"
+}
```

changedOutput schema / properties / summary / required

Previous value: -[
-  "tokenReference",
-  "literal",
-  "scssExpression"
-]New value: +[
+  "tokenReference",
+  "literal",
+  "scssExpression",
+  "composite",
+  "ambiguous"
+]

addedOutput schema / properties / tokens / items / properties / ambiguousValues

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "description": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "resolvedVia": {
+        "items": {
+          "$ref": "#/properties/tokens/items/properties/resolvedVia/items"
+        },
+        "type": "array"
+      },
+      "value": {
+        "type": "string"
+      },
+      "valueResolved": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "required": [
+      "value",
+      "description",
+      "valueResolved",
+      "resolvedVia"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / tokens / items / properties / composedOf

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "name": {
+        "type": "string"
+      },
+      "ref": {
+        "type": "string"
+      },
+      "resolvedVia": {
+        "items": {
+          "$ref": "#/properties/tokens/items/properties/resolvedVia/items"
+        },
+        "type": "array"
+      },
+      "value": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "required": [
+      "ref",
+      "name",
+      "value",
+      "resolvedVia"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / tokens / items / properties / declaredTimes
```
Added value: +{
+  "type": "number"
+}
```

changedOutput schema / properties / tokens / items / properties / valueType / enum

Previous value: -[
-  "token-reference",
-  "scss-expression",
-  "literal"
-]New value: +[
+  "token-reference",
+  "scss-expression",
+  "literal",
+  "composite"
+]

Addedv0.4.0Aug 10, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, but the description adds valuable behavioral context: it explains that --bsi- variables are safe to override at runtime and warns against overriding the central Design Tokens (--it-/$it-). It also clarifies the resolution chain and concrete value output, going beyond the read-only hint.

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 two sentences, tightly written, with no fluff. It front-loads the core purpose (lists CSS custom properties) and then adds essential usage nuance. Every sentence 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?

Given the tool's moderate complexity, an output schema exists, and the readOnly annotation is present, the description is adequately complete. It covers purpose, output details, and override safety. It does not discuss error cases or invalid component names, but these are not necessary for a list-style tool with a simple parameter.

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?

The input schema has one parameter with a description ('Component name or slug (e.g. "accordion", "Alert")') and schema_description_coverage is 100%. The description does not add any extra parameter-specific meaning beyond what the schema already provides, 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?

The description uses a specific verb ('Lists') with a precise resource ('CSS custom properties (--bsi-)... to customize a Bootstrap Italia component') and states the output fields (semantic description, resolvedVia, resolved value). This distinguishes it from sibling tools like tokens_list_globals (global tokens) and tokens_resolve (single token resolution).

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

Usage Guidelines4/5

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

The description clearly implies when to use this tool: when you need to customize a component via CSS overrides. It also provides crucial guidance that --bsi- variables are safe to override while --it-/$it- are not. However, it does not explicitly name alternative tools or state conditions when not to use it, though the context is strong.

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

Install Server

Other Tools

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Fupete/design-system-italia-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server