@depthark/css-first
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| suggest_css_solutionC | CSS-ONLY solution engine with strict enforcement of modern CSS features. Provides zero-JavaScript solutions using cutting-edge CSS (2021-2025) with logical properties, modern carousels, and light-dark() theming. |
| check_css_browser_supportB | Checks browser support for specific CSS properties using MDN data and provides detailed compatibility information. |
| get_css_property_detailsA | Retrieves comprehensive information about a CSS property from MDN documentation including syntax, examples, and use cases. |
| confirm_css_property_usageB | Confirms user consent for using a specific CSS property and provides implementation guidance. |
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 4 tools
Each tool has a clearly distinct purpose with no overlap: checking browser support, confirming user consent, retrieving property details, and suggesting solutions. The descriptions specify unique functions, making it easy for an agent to select the right tool without confusion.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., check_css_browser_support, get_css_property_details). The naming is predictable and readable throughout the set, with no deviations in style or convention.
With 4 tools, this server is well-scoped for its CSS-focused purpose. Each tool earns its place by covering distinct aspects of CSS development, from support checks to solution suggestions, without being too thin or bloated.
The tool set covers key workflows in CSS development: checking support, confirming usage, retrieving details, and suggesting solutions. A minor gap exists in direct manipulation or testing tools, but agents can work around this with the provided tools for most tasks.