8c312b37e2
We are now tracking whether a tool call event happens. We track generic "failure reasons" if the tool call fails. We DO NOT track names of tools, tool parameters, or any PII. Event name: - MCP tool called Properties: - is_execution_success - failure_reason - one of "missing requirements", "transport restriction", "error during tool execution", "unknown tool", "internal error calling tool" or doesn't exist in the case of successful tool execution. - arcade_mcp_server_version - runtime_language - os_type - os_release - device_timestamp As always you can opt out via setting the `ARCADE_USAGE_TRACKING` environment variable to 0.
12 lines
404 B
Python
12 lines
404 B
Python
# MCP Server Specific Event Names
|
|
EVENT_MCP_SERVER_STARTED = "MCP server started"
|
|
EVENT_MCP_TOOL_CALLED = "MCP tool called"
|
|
|
|
# MCP Server Specific Property Names
|
|
PROP_TRANSPORT = "transport"
|
|
PROP_HOST = "host"
|
|
PROP_PORT = "port"
|
|
PROP_TOOL_COUNT = "tool_count"
|
|
PROP_MCP_SERVER_VERSION = "arcade_mcp_server_version"
|
|
PROP_IS_EXECUTION_SUCCESS = "is_execution_success"
|
|
PROP_FAILURE_REASON = "failure_reason"
|