Connect Tool Library Skill

Manage HTTP API Credentials (tokens)

Credentials Config

• - Credentials File: INLINECODE0

Workflow

1. 1. If this skill's Credentials File is not exists, create it under this skill with followed content:

   # HTTP API Credentials
   ## Example
   - KEY_NAME: KEY_STRING
   ## Key List
   

1. 2. Save to Credentials File with format: INLINECODE1
2. Compare existing keys; if the key already exists, remove the old key pair
3. Compare existing key names; if the key name already exists, remove the old key pair

Execute Tool Calls

API Configuration

• - Base URL: INLINECODE2
• Authentication: Bearer token
• Token: Retrieve from users prompt
• Request Method: POST for all endpoints
• Content-Type: INLINECODE3

Available Endpoints

Fetch Tool Categories: POST /tool/categories

• - Returns list of all tool categories
• No request body required (send empty JSON {})
• Response Content-Type: INLINECODE6

Fetch Tool List: POST /tool/list/[CATEGORY_NAME]

• - Returns list of all available tools and tags. the format is :

  # Available Tools
  ## With Parameters
  - tool_name: tag
  ## No Parameters
  - tool_name: tag
  ## Tags
  - tag: tag_description
  

• - No request body required (send empty JSON {})
• Response Content-Type: INLINECODE9

Obtain Tool Description: POST /tool/description/[TOOL_NAME]

• - Return a specific tool description and input schema
• No request body required (send empty JSON {})
• Response Content-Type: INLINECODE12

Call Tool: POST /tool/call/[TOOL_NAME]

• - Executes a specific tool with provided parameters
• Request body: JSON object with tool parameters matching the tool's input schema
• Response Content-Type: INLINECODE14

Authentication Setup

Workflow

1. 1. Retrieve API Token from Credentials File
2. Check API Token, if the token start with $ then retrieve the real token from env
3. Fetch tool categories and select the best-suited one. If no category is selected, use category INLINECODE17
4. Fetch tool list and select the one best suited
5. If you need to view tool description or input schema, Obtain Tool Description
6. Call tool with parameters

Response Format

Important Notes

• - Authentication Required: All requests must include the bearer token in the Authorization header
• JSON Format: Request bodies must be valid JSON matching the tool's input schema
• Error Handling: Check isError field in responses to detect failures

Troubleshooting

• - Authentication Errors: Verify the bearer token is correct
• Tool Not Found: Check tool name spelling and fetch tool list
• Invalid Parameters: Review tool input schema for required fields