Skip to main content
Glama

Add a font file

add_font

Copies a TTF, OTF, TTC, or OTC font into a GlideDeck project’s assets folder so it stays with the presentation, then returns its family names for setting element fonts.

Instructions

Copies a .ttf/.otf/.ttc/.otc font file into the project's assets/ folder so it travels with the presentation, and returns its family names for update_elements (font).

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": {
      "path": "<path>",
      "font": "<font>"
    },
    "name": "add_font"
  }
}

Input Schema

NameRequiredDescriptionDefault
fontYesThe font file.
pathYesThe GlideDeck project file (.glide.json). Absolute, or relative to the server's folder; `.glide.json` is added when there is no extension.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and openWorldHint=false, so the description adds real value by disclosing the side effect (a file is copied into assets/) and the return payload (family names). It leaves duplicate/overwrite behavior and failure modes (bad extension, missing file) unstated.

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

Conciseness5/5

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

A single dense sentence with zero wasted words, front-loading the action and destination before the return-value note. The supported extensions and the downstream consumer are packed in without redundancy.

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?

With no output schema, the description helpfully states what comes back (family names) and how to use it, covering the main gap for a 2-parameter write tool with full schema coverage. Only edge-case behavior around duplicates or invalid files 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 coverage is 100%, so both `path` and `font` are already fully documented in the schema, making 3 the baseline. The description adds cross-tool meaning by tying the returned family names to update_elements' `font` argument, but says nothing extra about the parameters themselves.

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?

The description gives a specific verb (copies) plus resource (a .ttf/.otf/.ttc/.otc font file) and destination (the project's assets/ folder), so the operation is unambiguous. It does not explicitly distinguish itself from the sibling list_fonts or add_image, which is the only thing keeping it from a 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?

The rationale 'so it travels with the presentation' implies when to use it (bundling a font with the deck) and it points forward to update_elements with the `font` parameter. There is no explicit when-not guidance, such as using list_fonts for already-available fonts or skipping the copy when a system font suffices.

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