artiscene
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_categoriesA | List the articulated-furniture categories in the articraft catalog. |
| retrieve_articraftA | Retrieve articulated furniture records from one catalog category. |
| list_sessionsA | List every generated session (scene hash, status, quality). |
| get_session_reportA | Fetch the session report (status, quality, full report) for a scene hash. |
| generate_sceneA | Generate a sim-ready Isaac USD scene from a prompt. |
| resume_sessionA | Resume an existing generation session from a stage checkpoint. |
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 6 tools
Each tool targets a distinct action: listing sessions, listing categories, retrieving catalog records, fetching a specific report, generating a scene, and resuming a session. Even though list_sessions and get_session_report both concern sessions, one is enumeration and the other is a detailed single-item fetch, which is a standard CRUD distinction.
All tool names follow a consistent verb_noun pattern (list_sessions, list_categories, retrieve_articraft, get_session_report, generate_scene, resume_session). The verbs are lowercase and descriptive, and the nouns clearly indicate the object of operation.
6 tools is well within the ideal 3-15 range and matches the server's scope: catalog exploration, scene generation, session management, and reporting. No tool feels redundant.
The server covers the core workflow: discover categories, retrieve assets, generate scenes, list sessions, fetch reports, and resume from checkpoints. The only notable gap is the absence of a delete/archive operation for sessions, but that's a minor omission for this domain.