Portcullis is a gateway MCP server with 10 tools spanning server management, resource/tool/prompt/root listing, and health probing. All tools have descriptions (10-80 chars, mostly adequate). Input schemas are present for 6 tools (create_server, update_server, delete_server, get_server, trigger_health_probe, and the four list operations). However, descriptions are terse (many under 100 chars), parameter descriptions lack detail on constraints and formats, and output schemas are not documented. Error handling is minimal, no recovery guidance or actionable error messages visible. Tool naming is clear and verb-first, but composition could be tighter (e.g., roots/list, tools/list, resources/list, prompts/list are repetitive discovery tools that could be unified). Security is reasonable (RBAC filtering applied), but no evidence of rate limiting or input validation guidance.

• Document output schemas for all tools. E.g., 'list_servers returns {servers: [{slug, name, status, upstream_url, transport, auth_mode, health_status, last_health_check}], total: int}'.
• Convert 'transport' and 'auth_mode' parameters to enums with explicit allowed values in the schema. Add descriptions: 'transport: one of [streamable_http, stdio], the protocol used to communicate with the upstream MCP server.'
• Unify the four discovery tools into a single 'list_server_capabilities(slug: string, type: enum[tools|resources|prompts|roots]) -> {items: [...], total: int}' to reduce cognitive load.
• Add error recovery guidance to create_server and update_server: 'If upstream_url is unreachable, verify network connectivity and SSL certificates. Call trigger_health_probe to diagnose.'
• Implement a confirmation pattern for delete_server: require a 'confirm: true' parameter or add a separate 'confirm_delete_server' tool that must be called before deletion.

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

• Relies on Roots (deprecated) - pass files/dirs via tool parameters, resource URIs, or configuration