Skip to main content
Glama

Plan an agentic-os install

plan_install
Read-onlyIdempotent

Compose chosen role presets into an ordered file manifest with template URIs for review. This read-only step returns a plan without writing or modifying files.

Instructions

Compose one or more agentic-os role presets into an ordered manifest of the files an install should scaffold, each with a uri to read its template from. Use it after list_presets to turn chosen roles into concrete steps. Composition is additive: roles are unioned, the strictest HITL level wins, and every orchestration style in the union is installed. This returns a plan and writes nothing — no file is created, and the target repository is neither read nor touched, so the plan is not validated against what may already be installed (use run_doctor for that). You perform every write yourself, so the user can review each one. Read-only and idempotent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rolesYesRole preset names to compose, e.g. ["developer","qa"]. At least one is required. Get the valid names from list_presets — an unrecognized name is an error, not a silent skip, and no partial plan is returned. Composition is additive: pass every role the repo needs in one call rather than planning each separately.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
filesYesThe files to scaffold, ordered by template id. This is the plan's payload: you read each source_uri and perform the writes yourself. Any template with no file in the bundle is reported in follow_ups and omitted here rather than emitted as a broken entry.
rolesYesThe roles this plan composes, echoed back in the order given (which determines orchestration_default).
follow_upsYesProblems and decisions this plan could not settle — a missing template, an undeterminable HITL level or orchestration default. Surface these rather than installing past them: an empty array means the plan is complete as returned.
sdlc_skillsYesagentic-sdlc pipeline skills the composed roles enable. Empty if no chosen role takes part in the SDLC flow.
hitl_defaultYesThe human-in-the-loop level to install: the strictest among the chosen roles ("strict" > "gated-autonomous" > "autonomous"). Empty if no role declared a recognized level, in which case follow_ups says so.
generated_candidatesYesStack-specific agent contracts this role set *could* generate — candidates, not commitments. Generating one requires facts about the target stack that this server does not have, so filter them against the actual repository before writing any.
orchestration_defaultYesThe style to pre-select as active: the first listed role's default, except that a "strict" hitl_default forces "dispatcher". Empty if undeterminable, in which case follow_ups says to set it explicitly.
orchestration_installedYesEvery orchestration style to install — the union across roles, not a single choice, because a mixed team needs each one present.
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds valuable context: composition is additive, strictest HITL level wins, no file or repo touching, and the plan is not validated. No contradictions.

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 sentences, each essential. First states purpose, second gives workflow order, third details behavior. No filler, well-organized.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given rich annotations and 100% schema coverage, the description is complete: explains what, when, how, and key behaviors (read-only, idempotent, additive). No missing information for an AI agent.

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 description coverage is 100%, but the description adds meaning: roles must come from list_presets, unrecognized name is an error, and to pass all roles in one call. Does not repeat schema details.

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 verb 'Compose' and the resource 'agentic-os role presets into an ordered manifest of files'. It distinguishes from sibling tools like list_presets (role selection) and run_doctor (validation), and explicitly says 'returns a plan and writes nothing'.

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

Usage Guidelines5/5

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

Explicitly says 'Use it after list_presets to turn chosen roles into concrete steps' and provides an alternative: 'use run_doctor for that' for validation. Also notes to pass all roles in one call.

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/Jarroslav/agentic-os'

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