QVeris Tool Search & Execution

---

name: qverisai

description: Search and execute dynamic tools via QVeris API. Use when needing to find and call external APIs/tools dynamically — covers weather, search, stocks, finance, economics, geolocation, AIGC, news, social media, health data, and thousands more. Requires QVERIS_API_KEY environment variable.

env:

- QVERIS_API_KEY

requirements:

env_vars:

- QVERIS_API_KEY

credentials:

primary: QVERIS_API_KEY

scope: read-only

endpoint: https://qveris.ai/api/v1

auto_invoke: true

source: https://qveris.ai

examples:

- "Show me current weather in Tokyo"

- "Search for latest tech news"

- "Check Tesla stock price"

- "Analyze Apple's financial data"

- "What is the US GDP growth rate"

- "Generate an image of a sunset over mountains"

- "Get trending topics on Twitter"

- "Find clinical trials for diabetes treatment"

---

# QVeris Tool Search & Execution

QVeris provides dynamic tool discovery and execution - search for tools by capability, then execute them with parameters.

Setup

Requires environment variable:

No additional dependencies — uses Node.js built-in `fetch`.

Security

Quick Start

Search for tools

node scripts/qveris_tool.mjs search "weather forecast API"

Execute a tool

node scripts/qveris_tool.mjs execute openweathermap_current_weather --search-id <id> --params '{"city": "London", "units": "metric"}'

Script Usage

node scripts/qveris_tool.mjs <command> [options]

Commands:
  search <query>     Search for tools matching a capability description
  execute <tool_id>  Execute a specific tool with parameters

Options:
  --limit N          Max results for search (default: 10)
  --search-id ID     Search ID from previous search (required for execute)
  --params JSON      Tool parameters as JSON string
  --max-size N       Max response size in bytes (default: 20480)
  --timeout N        Request timeout in seconds (default: 30 for search, 60 for execute)
  --json             Output raw JSON instead of formatted display

Workflow

1. **Search**: Describe the capability needed (not specific parameters)

- Good: "weather forecast API"

- Bad: "get weather for London"

2. **Select**: Review tools by `success_rate` and `avg_execution_time`

3. **Execute**: Call tool with `tool_id`, `search_id`, and `parameters`

Example Session

# Find weather tools
node scripts/qveris_tool.mjs search "current weather data"

# Execute with returned tool_id and search_id
node scripts/qveris_tool.mjs execute openweathermap_current_weather \
  --search-id abc123 \
  --params '{"city": "Tokyo", "units": "metric"}'

Use Cases