ds-canon
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DS_CANON_FIXTURES | No | Path to a directory containing tokens.json, components.json, and conventions.md. If not set, the bundled Nimbus DS fixtures are used. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_tokensA | What tokens exist? Lists design tokens, optionally filtered by group, status, or a case-insensitive substring match on name and description. |
| get_tokenA | What is this token and who uses it? Returns full token detail plus the components that consume it, by exact name. |
| list_componentsA | What components exist? Lists component names, status, tags, and summaries, optionally filtered by status or tag. |
| get_componentA | What does this component look like? Returns full component detail: props, variants, tokens it consumes, and anti-pattern guidance, by exact name. |
| find_usagesA | What breaks if I change this? Reverse-dependency lookup for a token or component, by exact name. |
| whats_deprecatedA | What should I stop using? Lists every deprecated token and component, its migration target, and how many active entities still depend on it. |
| get_conventionsB | What are the house rules? Returns naming, spacing, color, accessibility, or deprecation conventions, optionally filtered to one topic. |
| check_token_driftA | Does this code drift from the token system? Scans a snippet for hardcoded hex colors and px values and suggests the matching or nearest token. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose: listing vs. retrieving specific entities, finding usages, checking deprecations, conventions, and code drift. The overlap between whats_deprecated and filtered token/component lists is minimal because the former is specifically about deprecated items and their migration targets.
Most tools follow a verb_noun pattern (list_tokens, get_component, find_usages, check_token_drift), but whats_deprecated breaks the pattern with a question-style name. Overall the naming is predictable and readable, with one minor deviation.
8 tools is well-scoped for a design system canonical server. Each tool addresses a distinct need (querying, detail lookup, dependency analysis, conventions, drift checking) and none feel redundant or unnecessary.
The tool surface comprehensively covers the design system domain: token and component listing/detail, deprecation info, reverse dependencies, conventions, and code drift detection. For a read-only reference server, the coverage is complete and leaves no obvious dead ends.