hermes_validate_api_configuration – 1 MCP server offers this tool
What it usually takes
additional_params– in 1 of 1base_url– in 1 of 1description– in 1 of 1endpoint– in 1 of 1header_keys_values– in 1 of 1mcp_api_key– in 1 of 1method– in 1 of 1name– in 1 of 1param_keys_values– in 1 of 1schedule_interval_minutes– in 1 of 1start_at– in 1 of 1stop_after_hours– in 1 of 1
No server marks it as only reading: treat it as able to change data.
From each publisher's own tool list. We never call a tool.
Servers
| Server | Inputs | Read-only? |
|---|---|---|
Hermes - Automated Asynchronous REST API Monitoring co.huggingface.agents-mcp-hackathon/hermes TOOL: Validate and store API configuration for monitoring. PURPOSE: Test an API endpoint and store the configuration if successful. This is STEP 1 of the monitoring setup process. If validation fails, retry with corrected parameters. If successful, use the returned config_id in activate_monitoring() function. CRITICAL: Even if success=True, you MUST manually check the 'sample_response' field before proceeding to activate_monitoring(). The API call may return success=True but contain error messages (like "401 Unauthorized", "Invalid API key", etc.) in the sample_response. CRITICAL: Always try to add parameters that will limit the API response to a manageable size. CRITICAL: Be sure to always clearly inform the user of the config_id after a desired validation result. CRITICAL: If you don't have an MCP API KEY given by the user, prompt them to get it here: https://mcp-hackathon.vercel.app/ WORKFLOW: 1. Call this function to validate API configuration 2. If success=False: Fix parameters | additional_params,base_url,description,endpoint,header_keys_values,mcp_api_key,method,name,param_keys_values,schedule_interval_minutes,start_at,stop_after_hours | Not stated |