Skip to main content
Glama

Search fonts

search_fonts
Read-only

Search Google Fonts and Fontshare for free typefaces by name or category. Get weights, variable status, CSS link for , and font page.

Instructions

Searches free fonts on Google Fonts and Fontshare. Returns weights, whether it is variable, the CSS link to paste in , and the font page. Without a query, returns the most popular in the category.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoName or part of it, e.g. inter, satoshi
sourceNoall
categoryNosans, serif, display, mono, handwriting or slab

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds meaningful context beyond them: which external sources are queried, the shape of the result (weights, variable flag, CSS link, font page), and the specific behavior when no query is supplied. It does not mention rate limits or pagination, but for a read-only search that is a minor gap.

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 short sentences, front-loaded with the core action and immediately followed by return contents and the empty-query rule. "The font page" is slightly vague, but nothing is padding.

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?

With no output schema, the description usefully enumerates the fields returned and covers the zero-required-parameter browse case, which is the main ambiguity for this tool. Only the limit and source parameters remain under-explained relative to a search tool of this complexity.

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 coverage is 50%, so half the parameters (limit, source) rely on defaults and the enum alone. The description partially compensates by naming the two supported sources and clarifying the query/category interaction when query is empty, but says nothing about limit or how results are ranked.

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?

States a specific verb and resource ("Searches free fonts") plus the two upstream sources and what is returned. The resource is naturally distinct from siblings like search_icons and search_components, but the description never explicitly contrasts itself with them.

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?

Implies usage through the no-query fallback ("Without a query, returns the most popular in the category"), which hints at browse vs. targeted lookup. It offers no explicit when-to-use/when-not guidance and never names an alternative tool for font-related follow-up work.

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