Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_categoriesA

List the articulated-furniture categories in the articraft catalog.

    Each entry pairs a category slug with the number of retrievable
    records it holds. Call this before retrieve_articraft to discover
    valid category names.

    Args:
        contains: Case-insensitive substring filter on the category
            slug; omit to list every category.

    Returns the matching categories, each with its record count.
    
retrieve_articraftA

Retrieve articulated furniture records from one catalog category.

    Each record is a URDF asset with meshes and physical joints that
    generate_scene can place. Use list_categories first to find valid
    category slugs.

    Args:
        category: Exact category slug from list_categories.
        query: Free-text description used to rank records within the
            category; omit to keep catalog order.
        top_k: Maximum number of records to return.

    Returns the ranked records with their ids and metadata.
    
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.

    Runs the full Shell->SceneReview pipeline; spends real LLM budget
    (bounded by the resolved budget cap) and takes minutes.
    
resume_sessionA

Resume an existing generation session from a stage checkpoint.

    Re-runs the pipeline from start_stage using checkpoints already on
    disk, writing a new revision and leaving prior revisions untouched.
    Cheaper than generate_scene when only later stages need to change;
    spends real LLM budget and takes minutes.

    Args:
        scene_hash: Session id from list_sessions or generate_scene.
        start_stage: First stage to re-run, one of "shell", "furniture",
            "physics", "scene_author", "scene_review".
        stop_stage: Optional last stage to run; omit to run to the end.

    Returns the new revision id, status, quality status, and cost.
    

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.3/5.0

Scored across 6 tools

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivitySlowing
ResponsivenessNo issues