Skip to main content
Glama

Fonts of a website

make_font_kit
Destructive

Read a web page to extract the fonts it uses, save each loaded font file with its license, and identify free alternatives for non-free fonts.

Instructions

Use it when the user wants the fonts a site uses, their files and licenses, or free fonts that match a site's type. Reads one page of a website in a headless browser and saves its fonts in one folder: which font draws its headings, body text, buttons and code, every font file the page loads, how each one is licensed, and the closest free font for each one that is not free. FONTS.md is the file to read first, fonts.css is for pages, with a variable for each role, and fonts.json for tools. The license of each font is written next to it so the user can decide what to use. It reads only the page at url, so a font used only on another page needs a run on that page, and a page that answers with an error gets no kit. For a whole brand kit with logos and colors, use make_brand_kit instead. The fonts playbook (makersmcp_playbook) has the whole job. (easyfontkit 0.1.5, on this machine.)

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": {
      "url": "<url>"
    },
    "name": "make_font_kit"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe page whose fonts to read, like https://linear.app. Only that page is read, and fonts can differ between pages, so give the one whose look is needed.
filesNoSave every font file the page loads in files/ (default true). Set to false to read the font files without saving them; fonts.css then loads none of the site's own files.
out_dirNoFolder to save into, absolute or relative to /app. Default: easyfontkit-<host>, where <host> is the site's host without www or the port. A run replaces what an earlier run of this tool left there once it has ended well, and one that fails or is canceled leaves it as it was: give each version its own out_dir. The folder must be empty or hold an earlier run of this tool: any other folder stops it.
wait_secondsNoHow long to wait for the result, counted from the start of the call, before returning a job_id to wait on. Some clients end a call after 60 or 240 seconds; 45 is safe in all of them.
timeout_secondsNoGive up after this many seconds (default 120). When a role shows a system font where the site's own was expected, its fonts may load late: try 240.

Output Schema

NameRequiredDescriptionDefault
kitYes
docsNoThe notes the text shows, and where each one is.
nextNoWhat to do next, as the Next line says.
toolYes
filesNo
folderNoWhere the kit saved its files.
job_idYes
passedNoFor checks: whether the check passed.
statusYes
continuedNoTrue when this call continued the job of an identical call whose answer did not reach the client, instead of starting another.
exit_codeNo
last_lineNoWhat the kit was doing last.
expires_atNoWhen the download links stop working.
next_actionNo
elapsed_secondsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.2.0
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / files / description
      Previous value: -"Set to false to read the font files without saving them."New value: +"Save every font file the page loads in files/ (default true). Set to false to read the font files without saving them; fonts.css then loads none of the site's own files."
    • changedInput schema / properties / out_dir / description
      Previous value: -"Folder to save into, absolute or relative to /app. Default: easyfontkit-{host}."New value: +"Folder to save into, absolute or relative to /app. Default: easyfontkit-<host>, where <host> is the site's host without www or the port. A run replaces what an earlier run of this tool left there once it has ended well, and one that fails or is canceled leaves it as it was: give each version its own out_dir. The folder must be empty or hold an earlier run of this tool: any other folder stops it."
    • changedInput schema / properties / timeout_seconds / description
      Previous value: -"Give up after this many seconds (default 120)."New value: +"Give up after this many seconds (default 120). When a role shows a system font where the site's own was expected, its fonts may load late: try 240."
    • changedInput schema / properties / url / description
      Previous value: -"The website, like https://linear.app"New value: +"The page whose fonts to read, like https://linear.app. Only that page is read, and fonts can differ between pages, so give the one whose look is needed."
    • changedInput schema / properties / wait_seconds / description
      Previous value: -"How long to wait for the result before returning a job_id to wait on. 45 is safe for clients that stop a tool call after 60 seconds."New value: +"How long to wait for the result, counted from the start of the call, before returning a job_id to wait on. Some clients end a call after 60 or 240 seconds; 45 is safe in all of them."
    • addedOutput schema / properties / continued
      Added value: +{
      +  "description": "True when this call continued the job of an identical call whose answer did not reach the client, instead of starting another.",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / docs
      Added value: +{
      +  "description": "The notes the text shows, and where each one is.",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "name": {
      +        "type": "string"
      +      },
      +      "path": {
      +        "type": "string"
      +      },
      +      "url": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "name"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / next
      Added value: +{
      +  "description": "What to do next, as the Next line says.",
      +  "type": "string"
      +}
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, and the description corroborates this by explaining that a successful run replaces a prior run's output while a failed or canceled run leaves it untouched, and that an erroring page yields no kit. It also discloses the async pattern (returning a job_id to wait on), which the annotations do not cover. It stops short of describing the on-disk layout in detail, but the output schema carries that.

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 intent and action, then outputs, then constraints and the sibling alternative — a sensible order with no filler sentences. It is on the long side and ends with version/machine metadata that adds little for tool selection, which keeps it below a 5.

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?

For an open-world, destructive, potentially long-running scrape-and-write tool, it covers intent, scope limits, failure behavior, the async job path, deliverable file names, and the sibling alternative. With an output schema present it need not detail return values, so nothing an agent needs to invoke it correctly is missing.

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 description coverage is 100%, so the schema already documents all five parameters thoroughly, including out_dir replacement semantics and the timeout rationale. The description reinforces the page-scoping meaning of url and points at FONTS.md as the first file to read, which adds orientation value but little that the schema lacks. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('Reads one page of a website in a headless browser and saves its fonts in one folder') and enumerates exactly what is captured: heading/body/button/code fonts, font files, licenses, and free alternatives. It also explicitly demarcates itself from make_brand_kit, so an agent can separate it from the nearest 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 the triggering user intent ('when the user wants the fonts a site uses, their files and licenses, or free fonts that match a site's type'), names the alternative for the adjacent case ('For a whole brand kit with logos and colors, use make_brand_kit instead'), and points to the playbook for the full workflow. It also states the key limitation that only the given page is read, so a font used elsewhere requires another run.

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