Skip to main content
Glama
Sign In
goldenratio-mcp

goldenratio-mcp

by truefrontier
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

tailwindcss-golden-ratio setup

tailwind_plugin_setup
Read-only

Generates Tailwind CSS plugin setup steps and exact theme values for golden-ratio spacing, widths, scale, font sizes, and borders from your chosen options.

Instructions

How to add the tailwindcss-golden-ratio plugin (the one goldenratio.app uses): install command, tailwind.config.js, options, and the exact theme values it generates (spacing, grp widths, scale, fontSize extras, borderWidth/lineHeight) for the given options.

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": "tailwind_plugin_setup"
  }
}

Input Schema

NameRequiredDescriptionDefault
prefixNotheme.goldenRatio.prefix (true = "gr-").
spacer_baseNotheme.goldenRatio.spacerBase: the size of spacer 6 (default 1.5, as on goldenratio.app).
spacer_unitNotheme.goldenRatio.spacerUnit (default 'rem').
use_css_varsNotheme.goldenRatio.useCssVars (default true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine value beyond that by disclosing the payload contents (install command, config file, options, and the exact generated theme values including spacing, grp widths, scale, fontSize, borderWidth/lineHeight). It stops short of stating the output format or that results are deterministic for a given option set.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with the core purpose front-loaded, followed by a parenthetical inventory of outputs. The parenthetical is long but each item is informative rather than filler. No redundant restatement of the title.

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?

There is no output schema, so the description must describe the return payload, and it does so concretely by listing install command, config snippet, options, and the exact generated theme values. The main missing piece is the response format (markdown vs. structured object) and whether it is static text or computed from the supplied options.

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?

Schema description coverage is 100% and all four parameters carry defaults, enums, and mappings to theme.goldenRatio.* keys, so the schema does the heavy lifting. The description only gestures at 'the given options' and lists the theme categories produced, without adding syntax or interaction detail. Baseline 3 is appropriate.

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 names the specific plugin (tailwindcss-golden-ratio) and enumerates exactly what the tool returns: install command, tailwind.config.js, options, and generated theme values. That is a concrete, verifiable purpose. It does not explicitly contrast itself with siblings like golden_css_variables or golden_spacing, so an agent must infer the boundary from the Tailwind-plugin framing.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the tool to call when a user wants to install/configure the Tailwind plugin. There is no explicit when-to-use, when-not-to-use, or named alternative among the six sibling tools. For a setup-oriented tool that overlaps conceptually with golden_css_variables, this is a real gap.

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