Skip to main content
Glama

Suggest Font Pairings

suggest_font_pairings

Get curated Google Fonts pairings for a chosen mood, with ready-to-paste @import rules and CSS font stacks that include safe fallbacks, so you can style typography without hunting for combinations.

Instructions

Curated Google Fonts pairings for a mood, with the @import and CSS font stacks (with safe fallbacks) ready to paste. Deterministic, no API key needed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "mood": "<mood>"
    },
    "name": "suggest_font_pairings"
  }
}

Input Schema

NameRequiredDescriptionDefault
moodYes
countNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/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 load, and it does disclose useful behavior: output is a curated (non-random) set, comes pre-formatted with @import plus fallback stacks, and requires no credentials. It still omits whether output format is text/markdown, how pairs are ordered, or whether the same mood always returns identical results guaranteed — 'deterministic' implies it but the shape of the response is unstated.

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: what you get first, then the behavioral guarantee. Nothing padded and no restating of the title.

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 simple two-parameter read-only tool with no output schema, the description is close to sufficient: it defines the deliverable format and the no-key/deterministic contract. The unexplained count parameter and absence of any guidance on selecting a mood leave real gaps that the schema cannot fill.

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 coverage is 0% and the description only gestures at 'mood', adding no meaning beyond the enum values themselves (e.g., what distinguishes 'editorial' from 'elegant' when choosing). The other parameter, count (1–5, default 3), is never mentioned in the description and has no schema text, leaving an agent to infer it means number of pairings.

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 the concrete resource (curated Google Fonts pairings) and its scoping dimension (a mood), plus the exact deliverable (@import rules and CSS font stacks with fallbacks). It stops short of an explicit verb phrase and never contrasts itself with nearby tools like generate_type_scale, so an agent must infer that this is the 'pick fonts' rather than 'build scale' tool.

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 statement of when to reach for this tool versus the font/type siblings, and no when-not guidance (e.g., when a full type scale or token extraction is the better call). 'Deterministic, no API key needed' is a property, not a usage condition.

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