Skip to main content
Glama
Sign In
Foldline

Foldline

by alireza12t
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Download optional big assets

fetch_assets

Downloads Foldline assets not included with the install—Kokoro voices, HDRI skies, or sampled instrument libraries—into the library folder for TTS and 3D-style rendering.

Instructions

Downloads assets that are not shipped with Foldline into its library folder: the Kokoro voice model (voice), the HDRI skies that 3D styles light with (hdri), or a sampled instrument library (instruments).

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": {
      "what": "<what>"
    },
    "name": "fetch_assets"
  }
}

Input Schema

NameRequiredDescriptionDefault
libNoFor instruments: which library.
whatYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations supply only openWorldHint=true, so the description must carry the behavioral load, and it does disclose the key trait: this writes files into the library folder rather than returning data. It omits download size, time, failure behavior, and whether re-running skips already-present assets – meaningful gaps for a large, side-effecting download.

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 front-loaded sentence: the action and destination come first, then the parenthetical list maps each enum value to its asset. No filler or repetition.

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 two-parameter download tool with no output schema and minimal annotations, the definition covers purpose and the `what` values but leaves the agent without preconditions (network, size, existing-asset behavior) and without any treatment of `lib`. Adequate but not fully self-sufficient.

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 50%. The description adds real meaning for the `what` enum (voice=Kokoro model, hdri=HDRI skies used by 3D styles, instruments=sampled instrument library), which the bare enum does not convey. It never mentions the `lib` parameter, its 'all' option, or that `lib` is only relevant when what=instruments.

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 (downloads) and resource (assets not shipped with Foldline), then enumerates the three asset classes the `what` enum selects: Kokoro voice model, HDRI skies, sampled instruments. An agent can tell immediately this is the asset-provisioning tool, distinct from render_* and check_* siblings.

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?

Usage is only implied by 'assets that are not shipped with Foldline' – the agent can infer you call it before rendering with a voice/HDRI/instrument that isn't bundled. There is no explicit when-to-use statement, no prerequisites (network access, disk space, whether it is idempotent if already downloaded), and no routing to check_voice or check_reading.

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

Deploy Server

Other Tools