Skip to main content
Glama

fluent_build

Compile Fluent (now-sdk) projects into installable app files by running now-sdk build. Enable frozen_keys in CI to fail builds when keys or sys_ids are out of date.

Instructions

Compile a Fluent (now-sdk) project into installable app files. Runs now-sdk build. Set frozen_keys=true in CI to fail when keys/sys_ids are out of date. REQUIRES FLUENT_ENABLED=true and WRITE_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_build"
  }
}

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.
source_mapNoWrite source-manifest.json mapping build output back to source
frozen_keysNoFail if keys/sys_ids are not up to date (CI builds)
error_on_conflictNoTreat Fluent vs XML sys_id conflicts as errors

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv5.0.1
    • addedInput schema / properties / async
      Added value: +{
      +  "description": "Run 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.",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / directory / description
      Previous value: -"Project directory (optional, defaults to cwd)"New value: +"Project directory (contains package.json). Defaults to the working directory."
    • addedInput schema / properties / error_on_conflict
      Added value: +{
      +  "description": "Treat Fluent vs XML sys_id conflicts as errors",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / frozen_keys
      Added value: +{
      +  "description": "Fail if keys/sys_ids are not up to date (CI builds)",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / source_map
      Added value: +{
      +  "description": "Write source-manifest.json mapping build output back to source",
      +  "type": "boolean"
      +}
  2. Addedv4.9.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, open-world operation. The description adds genuinely new context the annotations cannot express: the required environment flags and the CI failure semantics of frozen_keys. It stays silent on what build artifacts get written or overwritten on disk.

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?

Three tight sentences: purpose and underlying command first, then the CI nuance, then the prerequisites. Nothing is redundant or buried.

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?

For a build tool with no output schema, the definition covers what it does, its prerequisites, and the main CI flag, with async and directory behavior handled by the schema. A note on where artifacts land would make it 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 description coverage is 100%, so every parameter is already documented, including frozen_keys' CI-oriented behavior. The description's only parameter remark repeats the schema's frozen_keys wording rather than adding format, default, or interaction detail.

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 a specific verb and resource ('Compile a Fluent (now-sdk) project into installable app files') and names the underlying command, so an agent knows exactly what happens. It does not explicitly distinguish itself from near siblings such as fluent_pack or fluent_validate, which keeps it 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 Guidelines3/5

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

Gives one concrete usage context (CI builds should set frozen_keys=true) and hard preconditions (FLUENT_ENABLED and WRITE_ENABLED must be true). It offers no when-not guidance and never points at an alternative such as fluent_pack for packaging or fluent_validate for checks.

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