arcade-mcp/libs
Eric Gustin 8c312b37e2
Track whether a tool call event happened (#661)
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.
2025-10-30 13:19:46 -07:00
..
arcade-cli Fix MCP capabilities, examples, tests, and more (#657) 2025-10-30 11:59:00 -07:00
arcade-core Fix MCP capabilities, examples, tests, and more (#657) 2025-10-30 11:59:00 -07:00
arcade-evals MCP Local (#563) 2025-09-25 15:28:15 -07:00
arcade-mcp-server Track whether a tool call event happened (#661) 2025-10-30 13:19:46 -07:00
arcade-serve Release libs for arcade-mcp (#598) 2025-10-03 12:11:25 -07:00
arcade-tdk Release libs for arcade-mcp (#598) 2025-10-03 12:11:25 -07:00
tests Fix MCP capabilities, examples, tests, and more (#657) 2025-10-30 11:59:00 -07:00