Update documentation for tools.json logging

Co-authored-by: lpcox <15877973+lpcox@users.noreply.github.com>

Author: Copilot

AGENTS.md

@@ -382,6 +382,7 @@ DEBUG_COLORS=0 DEBUG=* ./awmg --config config.toml
   - `{serverID}.log` - Per-server logs (e.g., `github.log`, `slack.log`) for easier troubleshooting
   - `gateway.md` - Markdown-formatted logs for GitHub workflow previews
   - `rpc-messages.jsonl` - Machine-readable JSONL format for RPC message analysis
+  - `tools.json` - Available tools from all backend MCP servers (mapping server IDs to their tool names and descriptions)
 - Logs include: startup, client interactions, backend operations, auth events, errors
 
 **Per-ServerID Logging:**
@@ -406,6 +407,29 @@ DEBUG_COLORS=0 DEBUG=* ./awmg --config config.toml
 - The `payloadPreview` shows the first 500 characters of the JSON for quick reference
 - To access the full data with all actual values, read the JSON file at `payloadPath`
 
+**Tools Catalog (tools.json):**
+- The gateway maintains a catalog of all available tools from backend MCP servers in `tools.json`
+- Located in the log directory (e.g., `/tmp/gh-aw/mcp-logs/tools.json`)
+- Updated automatically during gateway startup when backend servers are registered
+- Format: JSON mapping of server IDs to arrays of tool information
+- Each tool includes: `name` (tool name without server prefix) and `description`
+- Example structure:
+  ```json
+  {
+    "servers": {
+      "github": [
+        {"name": "search_code", "description": "Search for code in repositories"},
+        {"name": "get_file_contents", "description": "Get the contents of a file"}
+      ],
+      "slack": [
+        {"name": "send_message", "description": "Send a message to a Slack channel"}
+      ]
+    }
+  }
+  ```
+- Useful for discovering available tools across all configured backend servers
+- Can be used by clients or monitoring tools to understand gateway capabilities
+
 ## Error Debugging
 
 **Enhanced Error Context**: Command failures include:

README.md

@@ -72,6 +72,7 @@ For detailed setup instructions, building from source, and local development, se
   - `{serverID}.log`: Per-server logs for easier troubleshooting
   - `gateway.md`: Markdown-formatted logs for GitHub workflow previews
   - `rpc-messages.jsonl`: Machine-readable RPC message logs
+  - `tools.json`: Available tools from all backend MCP servers
 - `-p 8000:8000`: Port mapping must match `MCP_GATEWAY_PORT`
 
 MCPG will start in routed mode on `http://0.0.0.0:8000` (using `MCP_GATEWAY_PORT`), proxying MCP requests to your configured backend servers.
@@ -400,6 +401,7 @@ The gateway creates multiple log files for different purposes:
 2. **`{serverID}.log`** - Per-server logs (e.g., `github.log`, `slack.log`) for easier troubleshooting of specific backend servers
 3. **`gateway.md`** - Markdown-formatted logs for GitHub workflow previews
 4. **`rpc-messages.jsonl`** - Machine-readable JSONL format for RPC message analysis
+5. **`tools.json`** - Available tools from all backend MCP servers (mapping server IDs to their tool names and descriptions)
 
 ### Log File Location
 
@@ -427,7 +429,8 @@ Example log directory structure:
 ├── slack.log          # Only Slack server logs
 ├── notion.log         # Only Notion server logs
 ├── gateway.md         # Markdown format
-└── rpc-messages.jsonl # RPC messages
+├── rpc-messages.jsonl # RPC messages
+└── tools.json         # Available tools
 ```
 
 **Using the environment variable:**