Skip to main content
Glama
Sign In

font-metadata

by io.github.lazymac2x
OverviewDiscussionsAdmin

suggest_pairings

Get font pairing recommendations with CSS snippets, compatibility scores, and curated rationale from design experts.

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": {
      "font_id": "<font_id>"
    },
    "name": "suggest_pairings"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of pairing suggestions (1-10, default 5)
styleNoFilter by style: modern, elegant, bold, minimal, classic, etc.
font_idYesFont slug or family name to find pairings for
use_caseNoFilter by use case: editorial, blog, saas, tech, luxury, corporate, etc.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden. It adds value by specifying the outputs (CSS snippets, compatibility scores, curated rationale) and the design-expert sourcing, giving insight into expected behavior. It implies a read-only operation, which is adequate for a recommendation tool, though it doesn't explicitly state side-effect-free or permission requirements.

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?

The description is a single, well-structured sentence that front-loads the main action and enumerates key outputs. It is highly concise with no filler, maximizing information density.

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?

Despite no output schema, the description enumerates the core return components (CSS snippets, compatibility scores, rationale), which is sufficient for a simple suggestion tool. The parameters are fully documented in the schema, so completeness is adequate, though a bit more detail on the response structure would be beneficial.

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?

The schema covers all four parameters with descriptions (100% coverage). The description itself does not add meaning beyond the schema, so the baseline score of 3 applies. No additional parameter context is provided.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function: get font pairing recommendations with specific output types (CSS snippets, compatibility scores, rationale). This distinguishes it from siblings like generate_css (which generates CSS for a single font) and get_font_info (which returns font metadata).

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?

The description implies usage when font pairings are needed but provides no explicit guidance on when to use this tool versus alternatives. There is no mention of exclusions or alternative tools for related tasks, leaving the agent to infer the context.

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

All font-metadata toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources