livekit-agent-simulator
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| init_projectA | Scaffold |
| list_scenariosC | List all scenarios in |
| validate_scenarioC | Validate a scenario file: schema, required Persona brief, PassCriteria lint. |
| export_scenarioC | Export a parsed scenario (Persona, Execute run params, Dispatch flag, PassCriteria) as JSON. |
| run_scenarioC | Run a simulation (alias: prefer execute_scenario for validate-then-run). |
| execute_scenarioA | Validate then execute one scenario from |
| execute_scenariosA | Execute multiple scenarios. Omit scenario_ids to run all valid files; optional tag filter (e.g. smoke). |
| get_run_statusA | Status of a run from SQLite: running / done / failed, turn count, duration. |
| get_run_logC | Read events.jsonl with filters. |
| get_run_reportC | Full report: summary, judge verdict, suspicious turns, paths to timeline/events. |
| compare_runsB | Diff two runs: duration, turns, tool errors, turn-taking percentiles, verdicts. |
| list_runsC | Run history from SQLite, newest first. Optionally filter by scenario_id. |
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 12 tools
Most tools have distinct purposes (scaffolding, scenario management, execution, analysis). However, 'run_scenario' is an alias for 'execute_scenario', creating redundancy and potential confusion. Otherwise, boundaries are clear.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., 'list_scenarios', 'validate_scenario', 'compare_runs'). No mixing of conventions.
12 tools is well-scoped for a simulation framework: covering project initialization, scenario management, execution, validation, and results analysis. Each tool serves a clear purpose.
The tool surface covers the core workflow (init, validate, execute, analyze). Minor gaps: no direct tool for creating/editing scenarios (only export) and no deletion management. The redundant alias is a slight detraction.