This server has critical definition gaps. Tool schemas are not visible in source code, only script names and informal descriptions appear. No JSON Schema definitions, parameter types, or structured output schemas are documented. Descriptions are present but lack LLM-optimized structure (no WHAT/WHEN/HOW clarity). Tool names are somewhat action-oriented but lack verb-noun consistency. No error handling guidance, no parameter constraints, no output field documentation. This is a shell-script-based tool wrapper, not a properly structured MCP server with formal tool definitions.

• Define formal JSON Schema for each tool with input parameters (type, description, enum/pattern constraints) and output fields. Example: awsAuthRefresh should declare inputs (profile: string, timeout: number) and outputs (status: string, remaining_seconds: number, message: string).
• Rewrite tool descriptions as: '[ACTION] [WHEN] [RETURNS] [ERRORS]'. E.g. 'Refresh expired AWS credentials by running auto-login command. Call when Bedrock auth fails. Returns remaining session time or error message with recovery hint.'
• Rename tools to verb-noun format: 'check_aws_credentials' (UserPromptSubmit), 'get_aws_status_line' (statusLine), 'refresh_aws_auth' (awsAuthRefresh), 'export_aws_credentials' (awsCredentialExport).
• Add parameter descriptions and constraints. E.g. profile parameter: 'AWS profile name from ~/.aws/credentials (string, 1-64 chars, alphanumeric + dash/underscore)'. timeout: 'Max seconds to wait for auto-login (integer, 1-300, default 180)'.
• Document output schemas with field types and meanings. E.g. awsCredentialExport returns {Credentials: {AccessKeyId: string, SecretAccessKey: string, SessionToken: string}}. Include error responses: {error: string, recovery_hint: string, retryable: boolean}.