Inkbolt

Overview Schema Source Related Servers Discussions Admin

inkbolt_font_import

Idempotent

Import a permitted local outline font and its UTF-8 license, publish immutable byte and license copies to an explicit store, and return a pinned descriptor.

Instructions

Read a permitted local outline font and its UTF-8 license. Publish immutable byte and license copies to an explicit store; returns a pinned descriptor.

Input Schema

Name	Required	Description	Default
`face_index`	No
`store_root`	No	Runtime path relative to the selected workspace, or an absolute path inside it. Omitted session, receipt, job, image/font store and output roots use documented workspace defaults; explicit null retains optional-root semantics.
`source_path`	Yes	Runtime path relative to the selected workspace, or an absolute path inside it. Omitted session, receipt, job, image/font store and output roots use documented workspace defaults; explicit null retains optional-root semantics.
`license_path`	Yes	Runtime path relative to the selected workspace, or an absolute path inside it. Omitted session, receipt, job, image/font store and output roots use documented workspace defaults; explicit null retains optional-root semantics.
`response_format`	No	JSON/Markdown include a metadata envelope in text. Structured/preview use summary text. All formats send PNG bytes once with payload references.	json

Output Schema

Name	Required	Description	Default
`ok`	Yes
`error`	No
`result`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 16, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false), and the description adds real context beyond them: the source is a local file, copies are published as immutable bytes plus license, and a pinned descriptor is returned. It aligns with the idempotent hint via 'immutable' and does not contradict. Permission/error behavior is still 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?

Two front-loaded sentences with no filler; the read/publish/return sequence is ordered and each clause carries distinct 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?

An output schema exists so return values need not be explained, and schema coverage is high. However, for a write-to-store tool the absence of any usage/routing guidance and any note on the 'permitted' permission requirement leaves meaningful gaps.

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 80%, so the baseline is 3. The description loosely maps to source_path/license_path ('local outline font', 'UTF-8 license') and store_root ('explicit store'), but adds no format, syntax, or default details beyond the schema.

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?

States specific verbs (read, publish) and resources (local outline font, UTF-8 license, store, pinned descriptor), which is well beyond a tautology. It does not explicitly name a sibling to differentiate from (e.g. inkbolt_asset_import), so it stops short of 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The word 'permitted' hints at a prerequisite, but there is no explicit when-to-use, when-not-to-use, or alternative tool guidance. An agent gets no routing help against the large sibling set (asset_import, session_*, document_*).

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