hermes_activate_monitoring – 1 MCP server offers this tool
What it usually takes
config_id– in 1 of 1mcp_api_key– 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: Activate periodic monitoring for a validated API configuration. PURPOSE: Start automated recurring API calls based on a previously validated configuration. This is STEP 2 of the monitoring setup process. PREREQUISITE: Must call validate_api_configuration() first and obtain a config_id from successful validation. Make sure that the sample_response is what you expect to see before proceeding with this function. WORKFLOW: 1. First call validate_api_configuration() to get config_id 2. If validation successful, call this function with the config_id 3. Monitoring will run automatically according to the validated schedule ARGUMENTS: - config_id: The ID from successful validate_api_configuration() execution (required) - mcp_api_key: User's MCP API key for verification (must match validation step). Input Examples: 1. Activate scheduler for stock monitoring: config_id: 123456789 mcp_api_key: "your_mcp_key_here" 2. Activate scheduler for weather alerts: config_id: 987654321 mcp_api_key: "yo | config_id,mcp_api_key | Not stated |