Skip to main content
Glama

font-glyph-svg

Font to SVG: a line of text drawn as SVG paths from the font's own TrueType outlines — Reads a TrueType-outline font you supply as base64 (up to 2 MB; TTF, WOFF or WOFF2) and returns up to 200 characters of single-line text as an SVG made of outlines (one per distinct glyph, placed with ), plus each glyph's path data in font units (y up), for an agent producing a logo, icon label or image that must not depend on the font being installed. Composite glyphs and their transf

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": {
      "fontBase64": "<fontBase64>",
      "text": "<text>"
    },
    "name": "font-glyph-svg"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesOne line; line breaks are not laid out.
fontBase64YesBase64 of a .ttf, .otf, .woff or .woff2 file (not a .ttc collection), up to 2 MB.
fontSizePxNoDefault 100.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations at all, the description carries the whole behavioral burden, and it does disclose several important traits: a 2 MB input cap, accepted formats (TTF/WOFF/WOFF2, not .ttc), a 200-character single-line limit, and the output structure. However it never says how unmapped characters, invalid base64 or oversized fonts are reported, and the one caveat it does raise about composite glyphs is cut off mid-word, leaving the behavior unresolved.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is dense and front-loaded with the right facts, but it is delivered as one very long run-on sentence stuffed with parentheticals. It also terminates mid-word ("Composite glyphs and their transf"), so the reader is left with an incomplete clause rather than a structured caveat.

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?

There is no output schema, so the description must describe the return value, and it does: an SVG of <path> outlines, one per distinct glyph, composed with <use>, plus per-glyph path data in font units with y-up orientation. That is essentially complete for calling the tool correctly, with the only gap being the truncated composite-glyph caveat and missing error/missing-glyph behavior.

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% and each parameter already documents itself (text one line with no line-break layout, font file formats and size cap, fontSizePx defaulting to 100), so the baseline is 3. The description reinforces the 200-character and 2 MB limits but adds no new syntax or defaulting information beyond the schema, and fontSizePx is not mentioned at all.

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?

Names a concrete transformation: base64-encoded TrueType/OpenType font plus a line of text in, SVG built from <path> outlines plus per-glyph path data in font units out. That is a specific verb+resource statement an agent can match to a task without opening the schema, and it is far narrower than siblings like font-convert or svg-geometry.

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?

Supplies a clear usage context – "for an agent producing a logo, icon label or image that must not depend on the font being installed" – which tells the agent what class of task this serves. It gives no explicit exclusions or named alternatives (e.g. when to prefer font-convert or svg-geometry instead), so it stops short of full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources