hermes_retrieve_monitored_data – 1 MCP server offers this tool
What it usually takes
config_id– in 1 of 1mcp_api_key– in 1 of 1mode– 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: Retrieve monitored data for a specific API configuration. PURPOSE: Fetch the latest monitored data for a given configuration ID. This is STEP 3 of the monitoring setup process. PREREQUISITE: Must call validate_api_configuration() first and obtain a config_id from successful validation, then activate_monitoring() to start monitoring. This function can be called at any time after monitoring activation to retrieve the latest data collected by the monitoring system. ARGUMENTS: - config_id: The ID of the API configuration to retrieve data for (required) - mcp_api_key: User's MCP API key for verification (must match validation step). - mode: Data return mode - "summary" (LLM-optimized), "details" (full responses, minimal metadata), "full" (everything) Input Examples: 1. Retrieve data for stock monitoring: config_id: 123456789 mcp_api_key: "your_mcp_key_here" 2. Retrieve data for weather alerts: config_id: 987654321 mcp_api_key: "your_mcp_key_here". Returns: Dictionary with monitoring s | config_id,mcp_api_key,mode | Not stated |