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

ui-polish-mcp

by Pedro21062014
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_presets

List all available theme presets with their descriptions to understand your options and pick a suitable theme for your UI.

Instructions

Lista todos os presets de tema disponíveis com suas descrições.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_presets"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/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 transparency burden. The verb 'Lista' strongly implies a read-only operation, and 'com suas descrições' discloses the content of the return value. However, it does not mention output structure, ordering, or any potential limitations.

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, front-loaded sentence in Portuguese. Every word contributes meaningful information: the action ('Lista'), the scope ('todos os presets de tema'), and the output detail ('com suas descrições'). There is no filler.

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 zero-parameter listing tool with no output schema, the description is sufficiently complete: it states what is listed and what the descriptions include. It could add more about the return format or sorting, but this is a simple tool and the description covers the essential context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so the input schema has nothing to document. Per the baseline for zero-parameter tools, a score of 4 is appropriate; the description does not need to explain parameter meanings that do not exist.

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 uses a specific verb ('Lista') and a specific resource ('todos os presets de tema disponíveis'), and it adds what the output includes ('com suas descrições'). This clearly differentiates it from sibling tools like get_theme or suggest_theme, which perform different operations.

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?

There is no explicit guidance on when to use this tool versus alternatives such as get_theme or suggest_theme. The use case is only implicit from the action 'Lista', with no mention of when it should or should not be used.

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