mcp-netsuite-practice
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NETSUITE_MODE | No | Set to 'mock' (default) or 'sandbox' once a real client exists. | mock |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_stock_levelA | Return available warehouse units for an A-SAFE product SKU. Use when the user asks about inventory, stock on hand, or availability for a specific SKU (for example ASAFE-BARRIER-01). |
| get_order_statusA | Return the current status of a global sales order. Use when the user asks about an order, shipment progress, or fulfillment state for an order id (for example SO-10042). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools target completely distinct domains: inventory (stock levels by SKU) and order fulfillment (order status by ID). There is no overlap in purpose or arguments, so an agent can easily select the correct tool.
Both tools follow a consistent get_noun_noun pattern (get_stock_level, get_order_status), using snake_case and a clear verb prefix. The naming is predictable and uniform.
With only two tools, the server feels minimal. For a practice server this may be intentional, but it borders on too sparse to represent a meaningful integration, though each tool covers a distinct, useful query.
The tool surface only provides single-record lookups (by SKU and order ID) with no list, create, update, or delete operations. This is a significant gap for an ERP domain like NetSuite, where typical workflows require broader coverage.