This server provides 19 read-only tools querying Polish Parliament public data. Tool definitions are present with basic structure, but quality is inconsistent. Naming follows verb_noun convention well (get-*, all appropriate for query operations). Descriptions are minimal but present (average ~40-50 chars, below the 194-char baseline for A+ tools). Critical gaps: (1) Input schemas use raw Zod objects, not JSON Schema with explicit type declarations, schema quality is low-to-medium for most tools. (2) Parameter descriptions are bare and lack actionable detail (e.g., 'Offset for pagination' does not specify valid range, default, or when to use; 'Term of the Sejm' does not explain what values are valid or how to discover them). (3) Output schemas are completely undocumented, callers cannot know what fields to expect or how to chain results. (4) No error handling guidance: failures return plain text like 'Failed to fetch...' with no recovery steps. (5) STDIO-only transport (hard cap at 50). (6) No pagination limits documented despite many tools accepting offset/limit. These gaps prevent confident LLM-guided usage and increase hallucination risk.

• Convert Zod schemas to explicit JSON Schema format in tool registration. Ensure every parameter has 'type', description, and where applicable 'enum', 'minimum', 'maximum', 'pattern', or 'default' fields visible in the schema.
• Document output schemas for all tools. Add a 'Returns' section to each tool's code comment and/or server definition specifying the response structure (e.g., '{terms: Array<{id: number, name: string}>, total: number}').
• Expand parameter descriptions to 50 - 150 characters each. Example: 'offset (int, 0+): Number of records to skip for pagination. Default 0. Pair with limit for efficient pagination.' instead of 'Offset for pagination'.
• Expand tool descriptions to 100 - 200 characters. Example: 'Get a paginated list of all MPs serving in a specified Sejm term. Use this to discover MP IDs before calling get-member. Returns name, party, and committee affiliations.' instead of 'Get a list of MPs for a given term'.
• Add pagination constraints to all paginated tools. Document: 'limit: 1 - 100 (default 20). Requesting >100 items will be capped. Use offset to iterate.'
• Implement error recovery guidance. When a call fails, return structured error like: '{error: "Invalid term", message: "Term 15 does not exist. Valid terms: 1 - 11. Call get-terms() to list all.", retryable: false}'.
• Add 'when to use this tool' guidance to tool descriptions. Clarify overlapping tools (e.g., 'Use get-members for bulk MP data; use get-member for a single MP's detailed profile').
• Consider HTTP SSE or Streamable HTTP transport for remote accessibility. STDIO limits deployment to local/containerized environments only.