Skip to main content
Glama
Sign In
goldenratio-mcp

goldenratio-mcp

by truefrontier
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Golden grid

golden_grid
Read-only

Returns golden-ratio grid widths, starter container and row CSS, and every example row with its total width; optionally checks whether your own row adds up to exactly 100%.

Instructions

The golden grid from goldenratio.app/#/grid: w-grp-1..11, w-grp-half-, w-grp-double- percentage widths, the starter .container/.row CSS, every example row from the site with its total width, and an optional check of your own row (does it add up to exactly 100%?).

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

Input Schema

NameRequiredDescriptionDefault
rowNoWidths to check as one row, e.g. ["5", "4"] or ["half-4", "5", "half-4"] (w-grp- prefix optional).
container_pxNoAlso give each width in px for a row this wide.
include_examplesNoInclude the site example rows (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 safety is covered; the description adds genuinely useful behavior by disclosing the returned payload (class set, starter CSS, example rows with total widths) and the exact validation semantics ('does it add up to exactly 100%?'). It stops short of describing output format or ordering.

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?

One dense sentence with no filler, front-loaded with the source URL and then the payload contents. The enumeration is heavy but each item carries information; the trailing optional-check clause is the most useful part and is placed last.

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?

With no output schema, the description must convey what comes back, and it does: class names, container/row CSS, example rows with totals, plus check results. It misses response format/shape and the purpose of container_px, but an agent can call it correctly with what is given.

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%, so the baseline is 3; the description reinforces the row-check semantics ('does it add up to exactly 100%?') beyond the schema's format example. It never mentions container_px or that include_examples can be turned off, so it adds only marginal parameter meaning.

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 concretely enumerates what the tool surfaces from the goldenratio.app grid page: w-grp-1..11, half/double variants, starter .container/.row CSS, example rows with totals, and an optional row-sum check. That is specific enough to distinguish it from content-oriented siblings, but it is framed as a noun phrase plus content list rather than a clear 'returns X so you can do Y' statement, and it never names which sibling to use for the adjacent tasks.

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: you gather that you call it to look up grid widths/examples or to verify your own row ('an optional check of your own row'). There is no explicit when-to-use, when-not-to-use, or pointer to golden_calculator, golden_spacing, or golden_css_variables as alternatives.

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