Skip to main content
Glama
Sign In
goldenratio-mcp

goldenratio-mcp

by truefrontier
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Golden Calculator

golden_calculator
Read-only

Check whether two stacks of golden-ratio spacers (1–11) balance and list every spacer combination that makes the shorter side match.

Instructions

The goldenratio.app Golden Calculator. Stack spacers numbered 1-11 (each is the previous x 1.618) on a left and a right side; returns whether both sides are equal and, if not, every combination of spacers that would make the shorter side match ("Try" on the site). The site starts with left = [6, 5, 6], right = [].

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

Input Schema

NameRequiredDescriptionDefault
leftNoSpacer numbers stacked on the left, top to bottom, e.g. [6, 5, 6].
rightNoSpacer numbers stacked on the right.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.9/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 the safety profile is covered; the description goes further by describing the computation (each spacer is the previous × 1.618) and the return semantics (a boolean plus a list of balancing combinations). Since there is no output schema, that return-value explanation is genuinely additive. It omits nothing critical, though it says nothing about result size or cost when many combinations exist.

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?

Three sentences, front-loaded with the balancing rule before the return behavior and the default values. Every sentence carries information; only the opening "The goldenratio.app Golden Calculator" is mildly redundant with the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With two optional parameters, no output schema, and a simple read-only computation, the description covers the domain (what the numbers mean), the operation (balance check), the return (boolean plus candidate combinations), and the default inputs. An agent has everything needed to call it correctly without opening the schema.

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?

Schema coverage is 100%, so both parameters are already documented, and the baseline would be 3. The description earns above baseline by explaining what the integers mean (spacer numbers 1-11, each the previous × 1.618) and by giving the site's default stack, neither of which appears in the schema.

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 gives a concrete verb-and-resource picture: stack spacers numbered 1-11 on a left and right side, then check whether the two sides balance. It also states what is returned (equality plus every combination that would balance the shorter side), which makes the tool's role unmistakable. It stops short of naming any sibling tool by contrast, so 4 rather than 5.

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 implied rather than stated: the mention of "Try" on the site and the site's starting stack (left = [6, 5, 6], right = []) signals this is a balancing/verification tool, but there is no explicit when-to-use, no when-not-to-use, and no pointer to golden_spacing or the other siblings 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