Skip to main content
Glama

Generate Type Scale

generate_type_scale

Generate modular typography scales with matched line heights and optional fluid CSS clamp sizing that adapts text between mobile and desktop viewports.

Instructions

Generate a modular typography scale with matching line heights, optionally fluid (CSS clamp) so text scales smoothly between a mobile and desktop viewport. 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_type_scale"
  }
}

Input Schema

NameRequiredDescriptionDefault
baseNoBase font size in px
fluidNo
ratioNomajor-third
formatNocss
steps_upNo
steps_downNo
max_viewportNo
min_viewportNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose two useful behavioral traits: the operation is deterministic and requires no API key. However, it says nothing about how line heights are derived, whether fluid mode changes the scale formula, or what the returned payload looks like in each format.

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 tight sentences with zero waste, front-loading the core capability before the fluid option and the determinism note. Nothing redundant or buried.

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

Completeness2/5

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

For an eight-parameter generator with no annotations, no output schema, and near-zero schema descriptions, the description is too thin. An agent still cannot tell what the json format returns or how steps_up/steps_down shape the scale, which are the parameters most likely to be misused.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 13% (just 'base'), so seven of eight parameters depend on the description for meaning. It usefully explains the fluid/min_viewport/max_viewport relationship and hints at modular ratios, but leaves the ratio enum-vs-number duality, format (css vs json), and steps_up/steps_down entirely unexplained.

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 states a specific verb and resource ('Generate a modular typography scale with matching line heights') and adds a concrete output mode ('CSS clamp'). It is clearly distinguishable from sibling tools like generate_spacing_scale or generate_palette, though it never names or contrasts an alternative explicitly.

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 guidance and no mention of prerequisites or alternatives. The usage context (building a type scale with viewport-responsive sizing) is only implied by the phrasing, so an agent must infer the selection criteria.

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