orchestrui
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| inspect_projectA | Read bounded package.json, package-lock.json and components.json within the server working directory. Return a HostProfile with evidence; never execute project code. |
| list_librariesA | List the seven supported UI ecosystems and optionally filter by role. Returns metadata only. |
| recommend_stackB | Compute a minimal UI composition from structured host/task profiles, with task text supported as a legacy inference path. |
| get_library_guidanceB | Return use, avoid, compatibility, legal and official-source guidance for one ecosystem. |
| search_componentsB | Search a selected library's public official registry when available, with a verified metadata-only fallback. |
| get_install_instructionsB | Return an official install command as inert text. This tool never executes shell or package-manager commands. |
| audit_planC | Score a proposed library plan against the nine OrchestrUI quality and licensing categories. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct concern: listing ecosystems, inspecting projects, auditing plans, retrieving install commands or guidance, recommending stacks, and searching components. There is no meaningful overlap that would cause an agent to misselect.
All tool names follow a consistent snake_case verb_noun pattern (list_libraries, inspect_project, audit_plan, recommend_stack, search_components). Even the 'get_*' tools fit the pattern naturally and remain predictable.
Seven tools is well-scoped for a UI orchestration assistant. Each tool covers a distinct part of the workflow—discovery, inspection, planning, guidance, installation instructions, and component search—without bloat or redundancy.
The set covers the core workflow of inspecting a project, planning/recommending a stack, auditing it, and retrieving install/usage guidance. Minor gaps exist, such as no explicit library comparison or plan persistence/export tool, but these are workable around and not critical to the server's advisory purpose.