Single tool with partial schema and moderate description. The tool name follows verb_noun convention ('get_latest_liquidations'), but the schema is incomplete, parameter descriptions lack constraint details, and output format is unstructured markdown rather than typed JSON. The tool description is adequate (194 chars, within baseline), but parameter documentation is sparse. No output schema defined. Error handling is minimal. The server exposes an internal Context parameter to the tool definition, which is an implementation leak.

• Define output schema as a list of typed objects with fields: symbol (string), side (string enum: BUY|SELL), price (number), quantity (number), timestamp (ISO 8601 string), time_ago (string). Return JSON array, not markdown table.
• Add constraint details to 'limit' parameter: 'Integer between 1 and 1000. Defaults to 10. If omitted or exceeds 1000, server will use 1000.'
• Remove 'ctx' parameter from tool signature or mark it as internal/hidden so it does not appear in the LLM's tool definition. Use FastMCP's context injection internally.
• Add error recovery guidance: 'If no events are returned, the WebSocket connection may be initializing. Retry in 2 - 5 seconds, or check server logs for connection errors.'
• Return ISO 8601 timestamps (e.g., '2024-01-15T14:32:45Z') in the response instead of time-only strings. Include a computed 'seconds_ago' field for convenience.
• Document expected response format in tool description: 'Returns a list of liquidation events, each with symbol, side, price, quantity, and timestamp. Most recent events first.'

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

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