DAXQO Trajectory Collector MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DATA | Yes | Dataset root directory passed with --data, e.g. ./data. | |
| DEVICE_ID | Yes | Stable device UUID passed with --device-id, e.g. b683d45a-e298-40b3-90c2-3bcd8f59cb84. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| trajectory_recordC | Record one externally executed action; never performs device actions. |
| trajectory_statsB | Read local trajectory counts and quality statistics. |
| trajectory_exportC | Export a dataset under the operator-configured export directory. |
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 3 tools
Each tool has a clearly distinct action: recording, reading stats, and exporting. There is no meaningful overlap or ambiguity between them.
All tools follow the same trajectory_<action> convention with consistent snake_case and a shared domain prefix. The pattern is predictable and readable.
Three tools is well-scoped for a focused trajectory collector. Each tool earns its place and supports a core workflow stage.
The surface covers recording, observing statistics, and exporting data, which are the main lifecycle operations. Minor gaps exist around listing or inspecting individual trajectories, but agents can work around this through export.