Tiger MCP has 17 tools with complete names, descriptions, and input schemas visible in internal/mcp/server.go and related files. Naming follows verb_noun convention well (service_list, service_get, service_create, etc.), though there is tool-name repetition risk (14 of 17 start with 'service_'). Descriptions are present for all tools and range from 60-150 characters, meeting minimum length requirements. Input schemas are properly typed with JSON Schema format. However, OUTPUT schemas are not documented anywhere in the provided code, tools return results but the response structure is not specified, forcing LLMs to infer output fields. Error handling is mentioned as a feature but specific recovery guidance is not visible in tool definitions. Parameter descriptions are adequate but lack constraints (enums, format strings, min/max bounds) for many fields. The db_query tool exposes a 'query' parameter marked 'sensitive' but does not restrict it server-side, relying on client-side handling. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) are visible despite the risk classification being present (READ_ONLY, WRITE, REVERSIBLE, DESTRUCTIVE).

• Document the output schema for every tool. Include field names, types, and examples in the tool description or a linked schema. At minimum, specify: 'Returns an object with fields: id (string), name (string), status (string), created_at (ISO 8601), ...'
• Add enum constraints to parameters with fixed value sets. For service_create, specify: region_code must be one of [us-east-1, us-west-2, eu-west-1, ...]; service_type must be one of [TIMESCALEDB, POSTGRESQL]; environment must be one of [DEV, PROD].
• Expose tool annotations via the MCP protocol. Mark service_delete with destructiveHint=true; mark service_get, service_list, service_logs, db_query with readOnlyHint=true; mark service_start, service_stop, service_resize with idempotentHint=true.
• Rename tools to reduce 'service_' prefix ambiguity. Consider: 'list_services', 'get_service', 'create_service', 'delete_service' (or use domain-specific verbs like 'provision', 'retire'). Or group under a single 'services' tool with sub-operations.
• Add pagination parameters to service_list and service_backups. Include: limit (default 20, max 100), offset/cursor, and return a total_count or next_cursor. Document in description: 'Returns paginated results; default limit 20. Use offset to fetch additional pages.'
• Add a service_delete_confirm or dry-run mode. Offer a confirmation step before irreversible deletion: 'Call service_delete with dry_run=true to preview impact, then confirm with dry_run=false.'
• Document error responses with actionable guidance. In db_query description: 'If the query fails due to invalid syntax, the error will include the problematic line. If the service is not found, call service_list to verify the service_id.' In service_create, specify: 'Returns 400 if region_code is invalid; see region_code parameter for allowed values.'

Inferred effective spec: 2026-07-28+.

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