trocco-mcp-tools
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TROCCO_API_KEY | Yes | TROCCO API key for authentication | |
| TROCCO_BASE_URL | No | TROCCO API base URL | https://trocco.io |
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 |
|---|---|
| get_workflowA | Fetch a TROCCO workflow definition by pipeline_definition_id for read-only audit preparation. |
| get_datamartC | Fetch a TROCCO datamart definition by datamart_definition_id, including BigQuery SQL and option metadata when available. |
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
Both tools target distinct resources (datamart vs workflow) with no overlapping functionality, making them easily distinguishable.
Both tools follow the consistent verb_noun pattern (get_datamart, get_workflow), providing predictability.
Only two tools for a server named 'trocco-mcp-tools' is very limited; likely insufficient for a data platform's typical operations.
Only read operations (get) are provided; missing create, update, delete, and other lifecycle operations, leaving significant gaps.