qveris

Installation
SKILL.md

For more detailed discovery query formulation, tool selection criteria, parameter handling, and error recovery, see the Agent Guidelines.

When to use QVeris

Choose among connected tools and QVeris using task fit, data quality/freshness, cost, user constraints, and call overhead. Use QVeris when at least one of these is true:

  • the current environment lacks the required capability or live/structured data source;
  • the correct provider or API is not known in advance;
  • the task benefits from comparing providers on relevance, schema, quality, latency, or cost;
  • the preferred provider is unavailable or fails and a fallback is needed;
  • the user explicitly asks to discover or call a capability through QVeris.

Local computation and transformations do not need QVeris. For qualitative pages, tutorials, or factual browsing, use an available browsing tool unless structured API data or provider routing is required.

When external functionality is needed, follow this two-phase workflow. Discover, Inspect, Probe, and Call are independent protocol actions, not four mandatory steps.

Phase 1: Find and Call Services via MCP

Installs
5
GitHub Stars
262
First Seen
Jun 20, 2026