Skip to main content
Glama
nami2111

junobuild-mcp-server

by nami2111

Juno Config Init

juno_config_init
Idempotent

Initialize a juno.config file for your satellite. Preview the config content or write it directly to disk, with support for TypeScript, JavaScript, or JSON formats.

Instructions

Generate a juno.config file (TypeScript, JavaScript, or JSON). By default returns config content for preview. Set writeFile to true to write the file directly to disk. Then run juno_config_apply to push the config to your satellite.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoCustom file path for the config (defaults to juno.config.ts/js/json in project root)
formatNoConfig file formattypescript
sourceNoBuild output directory (e.g. dist, build, out)dist
multiEnvNoGenerate multi-environment config with staging and production satellite IDs
orbiterIdNoOptional Orbiter ID for analytics
writeFileNoWrite the config file directly to disk instead of returning content for preview
satelliteIdNoSatellite ID for production environment. Use a real ID or leave the placeholder.aaaaa-bbbbb-ccccc-ddddd-cai
stagingSatelliteIdNoStaging satellite ID (required if multiEnv is true)
Behavior4/5

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

Discloses default behavior (preview) and writeFile option. Aligns with annotations (idempotent, non-destructive). No contradictions; adds meaningful context beyond annotations.

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 sentences, front-loaded with purpose and followed by actionable workflow. No wasted words.

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?

Given 8 parameters and no output schema, the description sufficiently explains purpose, options, and follow-up tool. Could mention return value format, but adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers all 8 parameters (100%). Description adds workflow context (preview/write, multi-env) beyond schema definitions, justifying an above-baseline score.

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?

The description clearly states the tool generates a juno.config file in TypeScript, JavaScript, or JSON, and differentiates from sibling juno_config_apply by noting it's for generation before pushing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Indicates when to use (generate config) and mentions the next step (juno_config_apply). Provides context on preview vs writeFile, but lacks explicit when-not-to-use or alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nami2111/junobuild-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server