explain_results — TestWell Lab Tests MCP Prompt

explain_results is one of 2 prompts on the TestWell Lab Tests MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke explain_results from your client

• Claude Code TestWell Lab Tests Prompt/explain_results run in your project directory
• Claude Desktop TestWell Lab Tests Prompt/explain_results ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor TestWell Lab Tests Prompt/explain_results ~/.cursor/mcp.json
• VS Code TestWell Lab Tests Prompt/explain_results .vscode/mcp.json
• Zed TestWell Lab Tests Prompt/explain_results ~/.config/zed/settings.json
• Windsurf TestWell Lab Tests Prompt/explain_results ~/.codeium/windsurf/mcp_config.json
• Cline TestWell Lab Tests Prompt/explain_results ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI TestWell Lab Tests Prompt/explain_results ~/.gemini/settings.json
• Grok TestWell Lab Tests Prompt/explain_results .mcp.json (in your project root)
• ChatGPT TestWell Lab Tests Prompt/explain_results Settings → Connectors → Advanced → Developer mode
• Claude.ai TestWell Lab Tests Prompt/explain_results Settings → Connectors → Add custom connector
• LangChain TestWell Lab Tests Prompt/explain_results pip install langchain-mcp-adapters

Other prompts on this server

• price_a_test

TestWell Lab Tests also offers 2 resources — data you attach as context, where a prompt is something you run.

Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026. A listing does not declare its prompts, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each prompt's arguments.