This server has 2 tools with minimal documentation. Tool names are short and action-oriented ('add', 'which-app-on-port') but the latter is hyphenated and less conventional. No output schema is documented. Error handling is entirely absent, no recovery guidance, no error classification, no actionable messages. The 'add' tool is trivial; 'which-app-on-port' performs shell operations but provides no context about what fields the response contains or what errors might occur. If parameters lack descriptions, schema score cannot exceed 30.

• Add a description to the 'add' tool explaining its purpose: 'Adds two numbers together and returns the sum. Use this to perform arithmetic calculations.'
• Add a description to the 'which-app-on-port' tool: 'Identifies the process (command and PID) listening on a specified TCP port. Useful for checking which application owns a network port. Requires lsof and ps commands available on the system.'
• Add parameter descriptions to 'add': describe 'a' and 'b' as 'A numeric value to add' (or clarify if integers only).
• Add parameter description to 'which-app-on-port': describe 'port' as 'The TCP port number to query (1 - 65535).'
• Document the output schema for 'which-app-on-port': specify that it returns an object with 'pid' (string or null, the process ID) and 'command' (string, the process name).
• Wrap the 'which-app-on-port' implementation in a try-catch and return actionable error messages: 'Port {port} is not in use' or 'lsof/ps command not available on this system'.
• Consider renaming 'which-app-on-port' to 'get_process_on_port' or 'find_app_on_port' to follow verb_noun conventions and avoid hyphens.