get_wave_job_status — RQM WaveEngine Jobs MCP Tool Read-only
get_wave_job_status
(get wave job status) is one of 34 tools on the
RQM WaveEngine Jobs
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_wave_job_status from your client
- Claude Code RQM WaveEngine Jobs get_wave_job_status run in your project directory
- Claude Desktop RQM WaveEngine Jobs get_wave_job_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor RQM WaveEngine Jobs get_wave_job_status ~/.cursor/mcp.json
- VS Code RQM WaveEngine Jobs get_wave_job_status .vscode/mcp.json
- Zed RQM WaveEngine Jobs get_wave_job_status ~/.config/zed/settings.json
- Windsurf RQM WaveEngine Jobs get_wave_job_status ~/.codeium/windsurf/mcp_config.json
- Cline RQM WaveEngine Jobs get_wave_job_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI RQM WaveEngine Jobs get_wave_job_status ~/.gemini/settings.json
- Grok RQM WaveEngine Jobs get_wave_job_status .mcp.json (in your project root)
- ChatGPT RQM WaveEngine Jobs get_wave_job_status Settings → Connectors → Advanced → Developer mode
- Claude.ai RQM WaveEngine Jobs get_wave_job_status Settings → Connectors → Add custom connector
- LangChain RQM WaveEngine Jobs get_wave_job_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http waveengine https://jobs.rqmtechnologies.com/mcp/waveengineOther tools on this server
- list_buyer_jobs
- search_buyer_jobs
- list_wave_capabilities
- get_wave_capability
- run_buyer_job
- wave_gate_signal_capture_v1
- wave_diagnose_multichannel_capture_v1
- wave_measure_phase_drift_v1
- wave_extract_wave_features_v1
- wave_reconstruct_bounded_capture_v1
- wave_equalize_pilot_capture_v1
- wave_transport_polarization_frame_v1
- wave_generate_validated_signal_fixture_v1
- wave_compare_waveform_captures_v1
- wave_fit_coupled_channel_model_v1
- wave_verify_wave_pipeline_v1
- wave_rotate_and_validate_two_channel_frame_v1
- wave_convert_capture_to_spectrum_v1
- wave_reconstruct_time_domain_signal_v1
- wave_optimize_processing_pipeline_v1
- wave_compile_curated_processing_recipe_v1
- wave_apply_verified_phase_correction_v1
- wave_validate_spectral_criteria_v1
- wave_validate_reconstruction_quality_v1
- wave_compare_pipeline_responses_v1
- search_wave_capabilities
- get_wave_example
- run_wave_example
- estimate_wave_job
- run_wave_job
- get_wave_receipt
- get_wave_job_result
- get_wave_job_artifact
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.