Spaces:
Running
Running
Commit
·
0359cf2
1
Parent(s):
108dc63
Update activate_monitoring docstring to clarify prerequisites and emphasize sample_response validation
Browse files- api_monitor.py +5 -2
api_monitor.py
CHANGED
@@ -318,7 +318,10 @@ def activate_monitoring(config_id, mcp_api_key):
|
|
318 |
TOOL: Activate periodic monitoring for a validated API configuration.
|
319 |
|
320 |
PURPOSE: Start automated recurring API calls based on a previously validated configuration.
|
321 |
-
This is STEP 2 of the monitoring setup process.
|
|
|
|
|
|
|
322 |
|
323 |
WORKFLOW:
|
324 |
1. First call validate_api_configuration() to get config_id
|
@@ -326,7 +329,7 @@ def activate_monitoring(config_id, mcp_api_key):
|
|
326 |
3. Monitoring will run automatically according to the validated schedule
|
327 |
|
328 |
Parameters:
|
329 |
-
- config_id: The ID from successful
|
330 |
- mcp_api_key: User's MCP API key for verification (must match validation step)
|
331 |
|
332 |
Input Examples:
|
|
|
318 |
TOOL: Activate periodic monitoring for a validated API configuration.
|
319 |
|
320 |
PURPOSE: Start automated recurring API calls based on a previously validated configuration.
|
321 |
+
This is STEP 2 of the monitoring setup process.
|
322 |
+
|
323 |
+
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
|
324 |
+
to see before proceeding with this function.
|
325 |
|
326 |
WORKFLOW:
|
327 |
1. First call validate_api_configuration() to get config_id
|
|
|
329 |
3. Monitoring will run automatically according to the validated schedule
|
330 |
|
331 |
Parameters:
|
332 |
+
- config_id: The ID from successful validate_api_configuration() execution (required)
|
333 |
- mcp_api_key: User's MCP API key for verification (must match validation step)
|
334 |
|
335 |
Input Examples:
|