Skip to main content
Glama
Sign In

Agentfonts

by com.agentfonts
OverviewDiscussionsAdmin

search_fonts

Read-only

Find fonts to license. Use this first when a user needs a typeface for a design, website, app or document. Filter by free text (family, classification such as 'humanist sans' or 'slab serif', tags), required tags, characters the font must support (e.g. 'åäöŊ' or the actual headline), script and maximum price for a licence type. Returns up to limit fonts (default 10), each with id, family, foundry, styles, scripts, classification, open-licence flag and from_price_usd for the smallest tier of the chosen use (desktop by default). Free and read-only. Next: preview_font or get_family with a returned id, then quote_license.

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
useNoLicence type the price filter and from-price apply to; default desktop
tagsNoAll must match: headline, body, condensed, newspaper, ui, print…
tierNofirst licence dimension: desktop computers, web visitors/month, app apps, ebook titles, server cores
limitNoMaximum number of fonts to return; default 10
queryNoFree text over family, classification and tags, e.g. 'condensed headline sans'
glyphsNoCharacters the font must support, e.g. 'åäöÅÄÖ' or a sample headline
scriptNolatin, latin-ext, cyrillic, greek
max_price_usdNoOnly fonts at or below this price for use/tier

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only supply readOnlyHint, and the description goes beyond them by describing the result payload (id, family, foundry, styles, scripts, classification, open-licence flag, from_price_usd) and the default page size of 10. It also clarifies that from_price_usd reflects the smallest tier of the chosen use, which is genuine behavioral context rather than annotation restatement. It does not disclose result ordering or whether results are exhaustive versus relevance-ranked.

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?

Purpose and the "use this first" directive are front-loaded, followed by filtering capabilities and then next steps — a sensible order. The middle sentence is long and packs many filters into one clause, costing some scanability, but no sentence is filler.

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

Completeness5/5

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

With eight all-optional parameters and no output schema, the description carries the burden of explaining returns, and it does so by enumerating the fields and the default limit. Cost model, read-only nature, and follow-on tools are all covered, so an agent can call this correctly without further context.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema only hints at: it links max_price_usd to a specific licence type and tier ("the smallest tier of the chosen use (desktop by default)") and explains that tags are conjunctive ("required tags") and that glyphs accepts either a character set or an actual headline. That crosses the bar for exceeding the schema alone.

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?

"Find fonts to license" gives a specific verb and resource, and the definition immediately frames it as the entry point of a workflow ("use this first"). The closing routing sentence ("Next: preview_font or get_family with a returned id, then quote_license") makes it distinguishable from every sibling without opening their schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the triggering context explicitly ("when a user needs a typeface for a design, website, app or document") and names the follow-on tools with the condition that selects them ("with a returned id"). There is no explicit when-not-to-use clause, but the downstream routing covers the realistic branching well.

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

All Agentfonts toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources