Skip to main content
Glama
Sign In

Valmera — AI Video Editor

by io.valmera
OverviewDiscussionsAdmin

Import font

import_font

Validates an uploaded TTF or OTF brand-font asset for embedding and prepares a sanitized subset. The license statement and explicit rights attestation accompany the import.

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": {
      "asset_key": "<asset_key>",
      "licence": "<licence>",
      "project_id": "<project_id>"
    },
    "name": "import_font"
  }
}

Input Schema

NameRequiredDescriptionDefault
attestNo
familyNo
licenceYes
asset_keyYes
project_idYesExplicit project identifier for this request. The connection's navigation pointer does not select the target.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / project_id / description
      Previous value: -"Required immutable scope for this call. Copy the id from list_projects/open_project/project_state; the active-project pointer is never used to guess."New value: +"Explicit project identifier for this request. The connection's navigation pointer does not select the target."
  2. Added

TDQS

B3.4/5.0
Behavior3/5

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

Beyond the annotations, the description adds useful behavior: validation of TTF/OTF files, preparation of a sanitized subset, and the need for a license statement and explicit rights attestation. It still leaves important operational details unstated, such as validation failure behavior, persistence of the imported font, and whether an existing font is replaced.

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?

The description is two focused sentences with little waste, and the core validation/preparation behavior is front-loaded. The second sentence is slightly passive but still carries relevant prerequisite information.

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 five-parameter import tool with no output schema and sparse schema descriptions, the definition gives enough context to understand the basic operation and key prerequisites. It is incomplete regarding required asset_key semantics, the optional family parameter, and what a successful sanitized subset result looks like.

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 low at 20%, and the description partially compensates by implying that the asset is TTF/OTF, that a license statement is required, and that rights attestation accompanies the import. It does not explain asset_key, family, or how attest relates to the optional boolean parameter, so the compensation is only partial.

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 states a specific operation on a specific resource: validating an uploaded TTF/OTF brand-font asset and preparing a sanitized subset. It is clear and avoids tautology, though it does not explicitly distinguish this from adjacent asset-import tools such as import_lut or set_brand_kit.

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?

It implies when to use the tool by naming brand-font assets for embedding and mentioning license and rights attestation prerequisites. However, it does not explicitly say when to use this instead of alternatives or when not to use it.

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

All Valmera — AI Video Editor 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