Skip to main content
Glama
Sign In
ui-polish-mcp

ui-polish-mcp

by Pedro21062014
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_theme

Retrieve complete design token sets for a chosen UI theme preset (studio, craft, data, flow, or brutal) to apply consistent styling.

Instructions

Retorna tokens completos de um preset específico. Presets disponíveis: studio | craft | data | flow | brutal

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": {
      "preset": "<preset>"
    },
    "name": "get_theme"
  }
}

Input Schema

NameRequiredDescriptionDefault
presetYesNome do preset

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It implies a read-only retrieval via 'Retorna' and lists available presets, but it does not disclose output format, error behavior, or side effects. For a simple getter this is acceptable but not rich.

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 short sentences with no filler. The first sentence states the core function, and the second lists the valid options. Every word 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?

For a single-parameter retrieval tool, the description is mostly complete: it explains the purpose and enumerates valid inputs. It lacks usage context and return structure, but the simplicity of the tool makes this a minor gap.

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 already fully documents the preset parameter with an enum and a description ('Nome do preset'). The description repeats the enum values, adding no new parameter-level meaning beyond the schema. Baseline 3 applies due to 100% schema coverage.

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 clearly states the tool's function: 'Retorna tokens completos de um preset específico' (returns complete tokens for a specific preset). It also lists the valid presets, which helps distinguish it from siblings like list_presets or suggest_theme.

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 about when to use this tool versus alternatives such as list_presets or suggest_theme. The description only states what the tool does, not when it should be preferred.

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

Deploy Server

Other Tools