observability-tool-call-tracking

Track tool executions with usage details and error information for observability.

Updated Jun 21, 2026

Search Tags:#error handling #observability #instrumentation #tool tracking #tool performance

Ready to run

npx skills add https://github.com/infantesromeroadrian/arca-agent --skill observability-tool-call-tracking

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: observability-tool-call-tracking
Source: https://github.com/infantesromeroadrian/arca-agent/tree/main/template/skills/observability-tool-call-tracking
Command: npx skills add https://github.com/infantesromeroadrian/arca-agent --skill observability-tool-call-tracking

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps in effectively tracking and instrumenting tool executions to understand agent behavior and diagnose failures.

Core Features & Use Cases

Instrumentation: Track tool calls, arguments, results, success/failure status, and execution time.
Safe Logging: Provide guidelines on what to log and what not to log for security and privacy.
Tool Categories: Specific attributes for different types of tools like search, HTTP, database, file system, and code execution.
Error Tracking: Identify and categorize errors for improved debugging.
Use Case: Use this Skill to monitor and analyze the performance of various tools in your workflow, ensuring they are functioning correctly and efficiently.

Quick Start

Use the observability-tool-call-tracking skill to instrument the 'web_search' tool with proper context and error handling.

Frequently Asked Questions about observability-tool-call-tracking

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I track tool execution time and errors for observability?▼

To track tool execution time and errors for observability, you need to instrument your tool calls to log arguments, results, success or failure status, and execution time. This provides the execution data needed for debugging.

What should I log when instrumenting tool calls without compromising security?▼

When instrumenting tool calls, you should follow safe logging guidelines to determine what to log and what to exclude. This ensures you capture necessary debugging context without compromising security or user privacy.

How do I monitor different tool categories like database and HTTP tools in a workflow?▼

To monitor different tool categories like database and HTTP tools, you should apply specific tracking attributes tailored to each tool type. This categorization helps analyze the performance and behavior of varied runtime tools.

Why does categorizing errors improve debugging for tool tracking?▼

Categorizing errors improves debugging for tool tracking because it identifies and groups specific failure types within your system. This structured error tracking isolates root causes faster than reviewing generic execution logs.

Can I use this tool tracking instrumentation in various runtime environments?▼

Yes, you can apply this tool tracking instrumentation across various runtime environments. The monitoring approach requires proper logging and error handling mechanisms configured for your specific execution context.

What is tool call instrumentation for agent observability?▼

Tool call instrumentation for agent observability is the process of tracking tool executions to understand agent behavior and diagnose failures. It logs usage details and error information to monitor system performance.