Discussions
SuiteWorld brings thousands of innovators, builders, and leaders together to learn, connect, and shape what’s next. This October, explore how to build a stronger foundation for growth through inspiring keynotes, major product reveals, hands-on sessions, and unforgettable moments—all in one place for our biggest event of the year. Join us
How should users be providing agents access to official NetSuite documentation?
Hey all,
I've recently been experimenting with NetSuite's MCP Standard Tools (SuiteApp) within a sandbox environment. More specifically, connecting this MCP to Microsoft's 365 Copilot Studio.
My goal is to build a custom 'CoPilot' agent that our staff can use to complete basic tasks and serve as an internal NetSuite knowledge base. So far, it's been going well.
However, during my experimentation, I've noticed the agent struggles to provide instructions; it will invent file paths, settings, views, and a multitude of other seemingly basic knowledge points. In summary, it needs more context.
I could enable web searches for answers, but that introduces its own issues. These results might be false or outdated, and most of the NetSuite documentation isn't publicly accessible. A better approach would be to offer more context while carefully managing the source.
Cheers,
lelborn - Always learning something the hard way. 👌