tracktion-engine-mcp
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 |
|---|---|
| search_te_classesC | Search for Tracktion Engine classes by name or description |
| get_te_class_docsA | Get detailed documentation for a specific Tracktion Engine class |
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 2 tools
Search and get-docs are clearly distinct operations: one discovers classes via query, the other retrieves detailed documentation for a specific class. No overlap or ambiguity.
Both tool names follow a consistent verb_noun pattern with the 'te' prefix (search_te_classes, get_te_class_docs), making the naming uniform and predictable.
Two tools is minimal but defensible for a focused documentation lookup server. It feels slightly thin, but the pair covers the essential search-and-retrieve workflow.
The search and get-docs pair forms a complete workflow for browsing class documentation. No critical operations like listing or cross-referencing are obviously required for the stated purpose.