Skip to main content
Glama
Sign In
goldenratio-mcp

goldenratio-mcp

by truefrontier
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Golden spacing scale

golden_spacing
Read-only

Returns the golden ratio spacing scale, exact px/rem values, CSS variable names, and a cheatsheet table to implement consistent spacing in Tailwind or CSS.

Instructions

The golden spacing scale (spacers 1-11 plus half-N and double-N) with exact values, px and CSS variable names, as used by goldenratio.app and the tailwindcss-golden-ratio plugin. With default options it also returns the rounded cheatsheet table from goldenratio.app/#/spacing.

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_spacing"
  }
}

Input Schema

NameRequiredDescriptionDefault
prefixNoPlugin prefix option, only changes tailwind_key (true = "gr-").
spacer_baseNotheme.goldenRatio.spacerBase: the size of spacer 6 (default 1.5, as on goldenratio.app).
spacer_unitNotheme.goldenRatio.spacerUnit (default 'rem').
root_font_pxNoRoot font size for px conversion of rem/em values (default 16).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuine behavioral context beyond that: the exact extent of the scale (1-11 plus half and double variants) and the fact that default options additionally emit the rounded cheatsheet table. It stops short of saying whether the values are computed locally or how the cheatsheet is structured.

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?

Two sentences, front-loaded with the identity of the scale and followed by the output/cheatsheet note. The branding references (goldenratio.app, tailwindcss-golden-ratio plugin) earn some keep as provenance but consume space that could have gone to sibling differentiation.

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 characterize the return value, and it does: exact values, px equivalents, CSS variable names, and an optional cheatsheet table under defaults. For a zero-required-parameter read-only generator this is close to sufficient; only the shape of the returned structure is left implicit.

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 coverage is 100%, so prefix, spacer_base, spacer_unit and root_font_px are already fully documented in the schema. The description's reference to 'default options' hints that the parameters alter output and that defaults reproduce goldenratio.app, which is mildly additive but no substitute for parameter detail. Baseline 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?

States a specific resource (the golden spacing scale, spacers 1-11 plus half-N and double-N) and what the output contains: exact values, px, CSS variable names. It is clear about what the tool produces, but it never distinguishes itself from the overlapping sibling golden_css_variables, whose scope the 'CSS variable names' phrase partly claims.

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 when-to-use, when-not-to-use, or alternative named. The only conditional statement ('with default options it also returns...') describes output variation, not tool selection. An agent must infer that this is the spacing-scale counterpart to golden_ratio_steps and golden_css_variables on its own.

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