Get desktop application:
View/edit binary Protocol Buffers messages
event_id is the unique identifier for this event. It is a generated UUID.
The start of the tool call in milliseconds since the Unix epoch
The end of the tool call in milliseconds since the Unix epoch
The name of the tool, e.g. get_dimentions, dbt build, get_mart_models
The arguments supplied to the tool, e.g. a list of metrics or a dbt CLI selector
An error message if the call fails
The user can optionally set their dev environment id to use tools like the execute_sql
The user can optionally set their prod environment id to use tools like list_metrics
The user can optionally set their user id to use tools like execute_sql
The user id found at ~/.dbt/.user.yml if present
The dbt Cloud host that the user configured
The multicell account prefix that the user configured: https://docs.getdbt.com/docs/cloud/about-cloud/access-regions-ip-addresses
Common dbt Platform context
The version of dbt_mcp being used (e.g. 0.8.2)
How the instance of dbt-mcp was authenticated. Only applicable to local MCP (e.g. env-vars, oauth, null)
The trace that this tool call is associated with, i.e., the tools it is called with for a single user message. Only applicable to tool calls within an agent run in the dbt Platform.
The list of disabled toolsets from the DISABLE_* environment variables or x-dbt-disable-toolsets header.
This list of disabled tools from the DISABLE_TOOLS environment variable or x-dbt-disable-tools header.
Indicates where this request is coming from with the user_agent header. This is only relevant for remote MCP. For local MCP, the user_agent can be attained from the enrichment field.
Attribution identifier for tracking. Uses the format "type__value" (e.g. "thread_id__<x-dbt-copilot-thread-id>"). Only applicable to tool calls within an agent run in the dbt Platform.