Skip to main content
Glama

fluent_pack

Read-only

Packages a built Fluent app into an installable artifact for deployment via now-sdk pack; requires FLUENT_ENABLED=true.

Instructions

Zip a built Fluent app into an installable artifact (now-sdk pack). REQUIRES FLUENT_ENABLED=true.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "fluent_pack"
  }
}

Input Schema

NameRequiredDescriptionDefault
asyncNoRun as a background job and return a job_id at once. Poll it with get_job. Calls that take longer than about 20 seconds switch to a job on their own.
directoryNoProject directory (contains package.json). Defaults to the working directory.
skip_package_inventoryNoDo not generate package_inventory.csv

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true; the description adds a genuinely useful environment-variable gate and names the artifact produced. It does not explain overwrite behavior for an existing artifact, where the zip is written, or what happens on failure. Note a mild tension: packing creates an artifact file (and by default package_inventory.csv), which sits uneasily with readOnlyHint, though this is a filesystem-output nuance rather than a direct contradiction of the described action.

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 short sentences: the action and its output first, the hard prerequisite second. Nothing is wasted and the critical env gate is impossible to miss.

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 only three optional parameters, no output schema, and annotations covering safety and openness, the definition is nearly sufficient; it even compensates for the missing output schema by naming the installable artifact. It could be stronger by stating the pre-condition that a build must exist and where the artifact lands.

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 all three parameters (async, directory, skip_package_inventory) are already fully documented in the schema, including the get_job polling behavior. The description adds no parameter-level meaning beyond this, which is the expected baseline when the schema carries the burden.

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?

Specific verb+resource: 'Zip a built Fluent app into an installable artifact', with the underlying CLI command in parentheses. An agent immediately knows this produces a deployable package. It does not explicitly position itself relative to fluent_build or fluent_install, though 'a built Fluent app' implies it operates on build output.

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 gating prerequisite 'REQUIRES FLUENT_ENABLED=true' is stated, and 'built' implies this runs after a build step. However, there is no explicit when-to-use vs when-not guidance, no statement that fluent_build must run first, and no mention of alternatives among the many fluent_* siblings.

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