Three tools with partial schemas and descriptions. manage_api_config and fetch_api_data have action/enum-like parameters but lack explicit enum constraints in schema. Descriptions are present (50-100 chars) but generic and lack WHEN/WHY guidance. api_data_preview has 10 parameters but many lack actionable constraints (max_rows, max_cols, preview_depth are unbounded integers). No output schemas documented. Error handling returns JSON but lacks recovery guidance. Tool names use underscores (good) but descriptions rely on emoji rather than clarity. No tool annotations (readOnlyHint/destructiveHint). Schemas visible but incomplete, parameters lack minima/maxima and enum constraints.

• Add explicit enum constraint to 'action' parameter in manage_api_config: {"type": "string", "enum": ["list", "add", "update", "delete", "validate", "test"]}
• Document output schema for each tool. E.g., manage_api_config returns {"success": boolean, "message": string, "data": object}. api_data_preview returns {"success": boolean, "preview": object, "api_info": object}.
• Add min/max bounds to numeric parameters: max_rows (1-1000), max_cols (1-100), preview_depth (1-10), truncate_length (10-10000).
• Rewrite descriptions to explain WHEN and WHY. E.g., 'Fetch data from a configured API endpoint and store results. Use this after previewing with api_data_preview to confirm the data structure. Returns storage_session_id for later retrieval.'
• Add tool annotations via FastMCP: @mcp.tool(annotations={"readOnlyHint": false, "destructiveHint": true}) for manage_api_config and fetch_api_data.

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry