Skip to main content
Glama

convert_font

Convert font files between TTF, OTF, WOFF, and WOFF2 formats, or generate a CSS @font-face snippet from an input font for web use.

Instructions

Convert font files. Input: ttf, otf, woff, woff2. Output: ttf, otf, woff, woff2, css (@font-face snippet). Requires fonttools: pip install fonttools brotli.

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": {
      "inputPath": "<inputPath>",
      "outputPath": "<outputPath>"
    },
    "name": "convert_font"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputPathYesAbsolute path to input font file
outputPathYesAbsolute path for output font file (include extension)
inputFormatNoInput format (auto-detected if not provided)
outputFormatNoOutput format (auto-detected if not provided)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

B3.4/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 burden. It does disclose two genuinely useful behaviors: the accepted format matrix and the runtime dependency ("pip install fonttools brotli"). It omits whether the output path is overwritten, whether directories are created, and what errors surface for unsupported conversions.

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, front-loaded statements with no filler; the format matrix and dependency note are compact and scannable. Slightly telegraphic, but nothing is wasted.

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 four-parameter conversion tool with a fully documented schema and no output schema, the description covers purpose, formats, and setup requirements. It is adequate but leaves open the write semantics of outputPath and the shape of success/failure responses, which matter because there is no annotation coverage.

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 100%, so baseline is 3. The description adds one piece of real meaning beyond the schema: that the css output option produces a @font-face snippet rather than a font binary. The format enumerations merely restate the schema enums.

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?

"Convert font files" is a specific verb plus resource, and the input/output format lists make the tool's scope unambiguous against generic siblings like convert_document or convert_archive. It stops short of naming a sibling, so it lands at 4 rather than 5.

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?

Usage is only implied: the agent can infer this handles a single font file, but nothing says when to prefer batch_convert for multiple files or get_supported_formats to check capabilities. The dependency note (fonttools + brotli) is a prerequisite hint, not usage guidance.

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