Skip to main content
Glama
Sign In

Montik

by app.montik
OverviewDiscussionsAdmin

Create font upload

create_font_upload

A link to add one custom font file (.ttf, .otf or .woff2, up to 30 MB) from your own machine to the workspace's fonts, good for 60 minutes and one upload. Run the curl command it returns; the reply is the font, and text and brand kits can then use its family. list_fonts shows what is there. For fonts on Google Fonts, use add_google_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": {
      "name": "<name>"
    },
    "name": "create_font_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesFile name with its extension, such as Oswald-SemiBold.ttf
familyNoFont family (default: from the file name)
weightNoWeight, such as 600 (default 400)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only say it is a non-read-only, non-destructive, closed-world write. The description adds the details that actually matter operationally: the returned link expires in 60 minutes, is good for a single upload, and the returned value is the font itself, after which text and brand kits can reference its family. It does not cover failure behavior (e.g. what happens if the link is never used) or interaction with an existing font of the same family, which keeps it short of a 5.

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 sentences, no filler, and the hard constraints (formats, 30 MB, 60 minutes, one upload) are packed into the opening sentence where they are needed first. The first sentence is somewhat run-on with stacked parentheticals, which slightly hurts scanability but nothing is wasted.

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?

There is no output schema, and the description compensates fully by explaining that the call returns a curl command and that executing it yields the font resource. Combined with the TTL, single-use limit, and the downstream effect on text and brand kits, an agent has everything needed to invoke and complete the flow correctly.

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 name, family, and weight are already fully documented with examples and defaults. The description mentions 'family' only in passing as something downstream kits consume, adding no format or defaulting detail beyond the schema. Baseline 3 is appropriate here.

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 ('add one custom font file ... to the workspace's fonts') and immediately bounds it by format and size. It also names the two siblings that could be confused with it — list_fonts and add_google_font — so the agent can route without opening a 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?

Gives an explicit when-not: 'For fonts on Google Fonts, use add_google_font.' It also names list_fonts as the way to inspect current state and describes the required follow-up action ('Run the curl command it returns'), so the agent knows this tool is only step one of a two-step flow.

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

All Montik toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources