Skip to main content
Glama
Sign In
goldenratio-mcp

goldenratio-mcp

by truefrontier
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Golden CSS variables

golden_css_variables
Read-only

Generate the :root block of golden-ratio CSS variables as goldenratio.app ships, in css, min, or json with configurable spacer base and unit. Use it to add golden spacing variables without Tailwind.

Instructions

The :root block of golden-ratio CSS variables (--golden-ratio-1..11, half-, double-, --gr) exactly as goldenratio.app ships it. Use without Tailwind.

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

Input Schema

NameRequiredDescriptionDefault
formatNocss (default, readable), min (one line, as in the site stylesheet) or json.
spacer_baseNotheme.goldenRatio.spacerBase: the size of spacer 6 (default 1.5, as on goldenratio.app).
spacer_unitNotheme.goldenRatio.spacerUnit (default 'rem').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false. The description adds that the output is an exact copy of what goldenratio.app ships, which signals fidelity and a closed-world source, but it doesn't explain how format=json alters the payload or whether variables are overridable.

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?

Two sentences, front-loaded with the resource definition and followed by a sharp usage constraint. There is no filler or repetition.

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 three-parameter CSS generator with no output schema, the description states what the payload is and its source of truth. The only material gap is that it doesn't clarify the return shape when format=json is selected, though the parameter schema gives enough context to call it.

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 the schema already documents format, spacer_base, and spacer_unit in detail. The description adds no parameter-specific guidance, so the schema carries the parameter semantics and the baseline of 3 applies.

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 exact resource—the :root block of golden-ratio CSS variables—and lists the variable families (--golden-ratio-1..11, half-*, double-*, --gr), so an agent knows precisely what it returns. It distinguishes the no-Tailwind path but does not explicitly contrast with the sibling tools golden_spacing or golden_grid.

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?

'Use without Tailwind' gives an implied condition for selecting this tool versus tailwind_plugin_setup, but the alternative is not named and there is no explicit when-not guidance. The usage context is clear but minimal.

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