qveris

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

When external functionality is needed, follow this two-phase workflow:

Phase 1: Discover Tools via MCP

1. Identify what tool capability the user needs
2. Call search_tools with a functionality description (not parameter names) — limit results to 10
3. Call execute_tool to test a candidate, passing parameters via params_to_tool
4. Repeat or broaden the search if no suitable tool is found

Phase 2: Generate Production Code

Once a suitable tool is identified, generate code that calls the QVeris REST API directly. Do not reuse the MCP tool-call result — produce standalone code the user can run.

• Read the API key from the MCP server config (QVERIS_API_KEY)
• Set a 5-second request timeout
• Handle errors by checking the success field and error_message
• Verify the response structure matches expectations before delivering to the user; if the call fails (invalid key, rate limit, tool not found), report the error and suggest corrective action