Three tools with minimal definitions. Schemas are empty objects with no properties defined. Descriptions are present but extremely terse (10-20 chars), below the 34-char p10 baseline. No error handling guidance, no output schema documentation, no parameter constraints. Tools appear to be read-only probes rather than substantive agent tools. This server is not suitable for agent integration.

• Expand tool descriptions to 50-200 characters. Example: 'dataset_count' → 'Returns the total number of datasets currently available in the Zürich CKAN open data catalogue. Use this to verify data freshness or as a baseline for monitoring.'
• Document output schemas explicitly. For dataset_count, specify: {"type": "object", "properties": {"count": {"type": "integer", "description": "Total number of datasets"}, "timestamp": {"type": "string", "format": "date-time", "description": "When the count was retrieved"}}}
• Add error handling guidance. Example: 'If the CKAN service is unreachable, returns HTTP 503 with message "CKAN catalogue unavailable. Retry in 30 seconds." This is retryable.'
• If tools accept any parameters in the future, add type and description to each. Use enums for constrained values, min/max for numbers, and format constraints for strings.
• Consider whether these three tools are sufficient for agent use cases. Liveness probes (health) are infrastructure concerns, not agent tools. Evaluate whether dataset_count and record_count serve a real agent workflow or are demo/test fixtures.

Inferred effective spec: 2026-07-28+.

• Relies on Stateful initialize / Mcp-Session-Id (removed; protocol is stateless) - make each request self-contained