OnlyFonts

Get a font

get_font

Read-onlyIdempotent

Use this when the person asks about one font: its weights and styles, its license, the languages it covers, or what to pair it with. id is a family's id, its name in lowercase with hyphens ("lora", "space-mono"). Not for the CSS that loads a font on a page. Answers one family: its name, page link, category, designer, license, every style it has, the languages it fully covers, the families that pair with it and the ones that look like it.

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": {
      "id": "<id>"
    },
    "name": "get_font"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	a family id from search_fonts ("lora"), or its name

Output Schema

Name	Required	Description	Default
`id`	Yes
`url`	Yes
`text`	Yes
`title`	Yes
`styles`	Yes
`license`	No
`similar`	Yes
`category`	No
`designer`	No
`pairings`	Yes
`languages`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds useful scope context: it answers exactly one family, and the id must be the lowercase-hyphen family form. It does not mention behavior on an unknown or misspelled id, which is the main remaining 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?

Front-loaded with the usage trigger, then the id format, then the exclusion, which is the right ordering. The closing enumeration of return fields is somewhat long and largely duplicates the output schema, so it costs a little 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?

For a single-parameter read tool with a full output schema and complete annotations, the definition covers when to call it, what the id looks like, and what it returns. Only failure behavior for a bad id is left unaddressed, a minor omission given the tool's simplicity.

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 a rule the schema omits: the id is the family name lowercased with hyphens, with worked examples ("lora", "space-mono"). That normalization detail is genuinely beyond what the schema states.

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?

States a specific verb and resource (get one font family) and enumerates the facets it answers: weights/styles, license, language coverage, pairings. It explicitly carves itself out from get_font_css with "Not for the CSS that loads a font on a page," so an agent can distinguish it from a sibling without opening either schema.

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

Usage Guidelines5/5

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

Opens with an explicit when-to-use trigger ("when the person asks about one font") and names the case it is not for (font-loading CSS). The id parameter description points back to search_fonts as the source of a valid id, giving the agent a discovery path rather than leaving it to guess.

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

All OnlyFonts tools Inspect

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

Need Help?