shadcn-ui-mcp-server

get_theme

Read-only

Retrieve a tweakcn theme's details by name or ID to access its configuration and styling.

Instructions

Get details of a specific tweakcn theme

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "themeName": "<themeName>"
    },
    "name": "get_theme"
  }
}

Input Schema

Name	Required	Description	Default
`themeName`	Yes	Name or ID of the theme to retrieve

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Aug 21, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations include readOnlyHint: true, which already signals a safe read operation. The description adds no behavioral context beyond that, but doesn't contradict the annotation. It doesn't mention error handling, response format, or any special behavior, leaving the annotations to carry the burden.

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 a single lean sentence with no redundant words. It is appropriately sized for a simple getter tool and earns its place without filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (one parameter, readOnly annotation, no output schema), the description is minimally adequate. However, it doesn't specify what 'details' include or the return value structure, which would be helpful since no output schema exists. It's not incomplete enough to be confusing, but lacks rich context.

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 schema describes the single parameter themeName as 'Name or ID of the theme to retrieve' with 100% coverage, so the schema fully handles parameter semantics. The description itself adds no extra meaning beyond what the schema provides, matching the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves details of a specific tweakcn theme, using a specific verb ('Get') and resource ('theme'). It distinguishes from list_themes by implying a single specific theme, but doesn't explicitly contrast with siblings like get_component or get_block.

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

Usage Guidelines2/5

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

No guidance is given on when to use this tool versus alternatives. It does not mention that list_themes should be used to find themes first, or that apply_theme is for modifying, providing no context for tool selection.

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

Deploy Server