Skip to main content
Glama

Generate Spacing Scale

generate_spacing_scale

Generate a consistent spacing scale from a base unit in px or rem, output as CSS or JSON. Create deterministic design tokens without an API key.

Instructions

A consistent spacing scale from a base unit (4 or 8 are common), in rem or px. Deterministic, no API key needed.

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

Input Schema

NameRequiredDescriptionDefault
baseNo
unitNorem
formatNocss

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description does carry some behavioral weight: 'deterministic' tells the agent output is stable and repeatable, and 'no API key needed' removes auth concerns. It does not say whether the call is purely computational with no side effects, nor anything about output shape such as how many steps the scale contains.

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 short, front-loaded statements with no filler: the first defines the output and its key parameter, the second disambiguates operational concerns. Every clause earns its place.

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

Completeness3/5

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

For a three-parameter generator with no output schema, the agent still cannot predict the result: the number of steps, the ratio progression, and the shape of the CSS versus JSON output are all unstated. It is adequate to call the tool but not to anticipate or validate its return value.

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 0%, so the description must compensate, and it partially does by explaining that 'base' is a unit value (4 or 8 being common). The two enum parameters (px/rem, css/json) are self-documenting in the schema, but the description adds no guidance on realistic base values against the 2–16 range or on default behavior.

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 a specific resource — a consistent spacing scale derived from a base unit — which clearly distinguishes it from siblings like generate_type_scale or generate_shadows. It lacks an explicit verb, but the generated artifact is unambiguous.

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: the agent can infer this is the tool for spacing tokens, and 'no API key needed' hints it is freely callable. There is no explicit when-to-use versus alternatives (e.g., generate_design_system or convert_tokens) and no stated prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.