should-i-render
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SHOULD_I_RENDER_DATA | No | Path to an alternative components.json snapshot to test with the same shape. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_componentB | Rank up to three verified, rendering React components for a UI task using prose, pattern, style, and measured harness results. Failure warnings are excluded. |
| palette_pickA | Return one to three curated four-color palettes by mood, with hex roles and copyable CSS variables. |
| check_componentA | Return the full verdict, skip conditions, and measured render, accessibility, bundle, bare, and provider facts. |
| alternativesA | Compare same-pattern candidates using their verdicts and measured harness results. |
| install_planA | List dependencies, bare-harness gaps, provider requirements, setup notes, license, author credit, measured review URL, source URL, and an exact shadcn command when supported. |
| skip_listA | Show failure warnings and the worst measured offenders in a pattern, optionally filtered by visual style. |
| find_templateA | Rank up to three complete React page templates for a product or business task. Templates with a failed accessibility audit are excluded from recommendations. |
| check_templateA | Return a template summary, stack, license, accessibility status, preview, source, download, and available palette variants. |
| template_planA | Return an exact clone and setup plan for a complete template, optionally selecting one of its built palette variants. |
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 9 tools
Most tools cleanly separate resource (component vs template) and action (find, check, plan, skip). The main ambiguity is between find_component and alternatives, since both rank or compare candidates using measured harness results, though one is top-N ranking and the other is explicit same-pattern comparison.
The dominant pattern is verb_noun (find_component, check_component, install_plan, skip_list, find_template, check_template, template_plan), which is predictable. Palette_pick reverses the order and alternatives is a bare noun, so there are minor deviations but no chaotic mixing of conventions.
Nine tools is a well-scoped set for a UI component/template recommendation service. Each tool covers a distinct stage in the workflow—discovery, inspection, comparison, planning, palette selection, and failure warnings—without redundancy.
The tool surface covers the full decision flow: find and compare candidates, inspect verdicts, get install/clone plans, select palettes, and view failure warnings. A minor gap is the lack of a direct tool to fetch or modify component source, though install_plan and check_template provide source URLs.