How to use armor-mcp for data observability over MCP

{
  "surface": "mcp.ai-anomalyarmor-armor-mcp",
  "package": "uvx [email protected]",
  "server": "armor-mcp/3.4.2",
  "protocol": "2024-11-05",
  "transport": "stdio",
  "tools": ["get_alerts_summary", "list_alerts", "list_inbox_alerts", "update_alert", "list_alert_rules", "create_alert_rule", "manage_alert_rule", "get_alert_trends", "get_alert_history", "get_api_key_info", "list_assets", "trigger_asset_discovery", "create_asset", "manage_asset", "get_lineage", "job_status", "cancel_job", "create_tag", "list_tags", "apply_tags", "get_coverage", "manage_coverage", "list_destinations", "setup_destination", "manage_destination", "manage_rule_destinations", "get_freshness_summary", "check_freshness", "setup_freshness", "list_freshness_schedules", "manage_freshness_schedule", "health_summary", "get_todays_briefing", "ask_question", "generate_intelligence", "investigate_asset", "get_investigation", "get_metrics_summary", "list_metrics", "create_metric", "manage_metric", "get_validity_summary", "list_validity_rules", "create_validity_rule", "manage_validity_rule", "recommend", "create_referential_check", "manage_referential", "get_schema_summary", "list_schema_changes", "create_schema_baseline", "enable_schema_monitoring", "disable_schema_monitoring", "get_schema_monitoring", "dry_run_schema"],
  "tool_count": 55,
  "init_times_ms": [696, 422, 430],
  "call_times_ms": [46, 35, 35],
  "p50_init_ms": 430,
  "p50_call_ms": 35,
  "calls_ok": 6,
  "calls_total": 6,
  "sample_call": {
    "tool": "get_alerts_summary",
    "args": {},
    "result_preview": "No API key configured. Set ARMOR_API_KEY env var or create ~/.armor/config.yaml"
  },
  "notes": "Protocol conformant. Needs ARMOR_API_KEY for actual data operations. Clean error handling — tool calls return structured text errors, not crashes. Version skew: npm says 0.9.1, serverInfo says 3.4.2."
}