This MCP server exposes only a single tool (get_current_config) with minimal definition quality. The tool lacks a complete input schema, has a generic description that doesn't guide LLM behavior, and provides no documented output structure. The codebase is a full Next.js application with admin UI and backend logic, but the MCP integration appears rudimentary, only one tool is implemented and registered. No parameter validation, error recovery guidance, or schema documentation is evident in the source. The server follows none of the 54 Agentic Tool Patterns and would not pass code review for production use.

• Define and document the complete input schema for get_current_config. Specify required vs optional parameters, types, constraints (enums for provider and timezone if bounded), and descriptions for each parameter.
• Expand the tool description to 100-200 characters with clear guidance: 'Fetches the active AI configuration for the current organization, including the LLM provider, model name, timezone for date operations, enabled search domains, assigned persona, and active skills. Call this once at session start to tailor subsequent operations to the configured environment.' This tells the LLM when and why to use it.
• Document the output schema as a structured object, e.g.: { aiModel: string, provider: enum[openai|anthropic|google], timezone: string, enabledDomains: string[], persona: object, enabledSkills: string[] }. Include descriptions for each field.
• Add parameter descriptions if any parameters exist. For example, if the tool accepts an 'org_id' parameter, describe it as 'The organization identifier (required if multi-tenant; defaults to the calling user\'s org).'
• Implement at least 5-10 additional core NetSuite tools to match the domain scope: get_record (read a single record), search_records (find records by criteria), create_record, update_record, delete_record, run_saved_search, get_list_values (for dropdowns/enums), execute_workflow, etc. Each should follow the pattern rubric.
• Add error handling guidance to the description: 'Returns 401 if credentials are invalid (re-authenticate); 403 if the user lacks permissions (contact admin); 500 if the config service is unavailable (retry after 30s).'