Server has 5 tools with complete input schemas and detailed descriptions. Naming follows verb_noun pattern (search_*, get_*). Descriptions are comprehensive (200-800 chars) and include context about dual-source aggregation, unit normalization, and area resolution. However, output schemas are not formally documented in the code, responses are described in prose within tool descriptions rather than as structured JSON Schema. Parameters are well-described with constraints (e.g., page defaults, limit clamping), but no explicit enum constraints for categorical values. Error handling is mentioned in descriptions but not formalized in tool definitions. Security is good (read-only operations, no secrets in params). Composition is sound, tools chain logically (search → get_supported_areas for validation).

• Add formal JSON Schema output definitions to each tool. Document the structure of 'items' array (fields: itemId, title, price_yuan, platform, bail_yuan, etc.) and 'meta' object (totalCount, page, pageSize, dropped, area_applied). This enables LLMs to extract and chain results reliably.
• Convert region parameters to enums or add a discovery tool. Call ali_get_supported_areas / jd_get_supported_areas to populate valid province/city/district values, then declare them as enums in search tools. Alternatively, add validation error messages that list valid options.
• Formalize error responses in tool schemas. Define error types: 'area_not_resolved' (user-fixable: call *_get_supported_areas), 'no_results' (retryable: try broader region), 'rate_limited' (retryable: wait). Include recovery guidance in each error.
• Add tool annotations. Mark all 5 tools with readOnlyHint=true and idempotentHint=true to signal they are safe to retry and do not modify state.
• Document parameter dependencies explicitly. In ali_search_judicial, jd_search_judicial, and search_judicial, add a note: 'city requires province; district requires city. Omit city/district to search at province/national level.' Consider adding a 'required_if' constraint in schema.

Inferred effective spec: 2026-07-28+.

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