Skip to main content
Glama
Sign In
netsuite-saved-search-mcp

netsuite-saved-search-mcp

by maximizeGPT
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_exports

Discover available NetSuite saved-search exports in a directory. Returns per-file summary including row count, headers, warnings, and date range.

Instructions

List every NetSuite saved-search export (.xls) in a directory under NSMCP_ROOT. Returns one ExportSummary per file with row count, header count, 0-indexed header_row, warning count, and detected date range. Files that can't be parsed even with lxml recovery come back with parse_error populated and the other fields None. Call this first when you don't already know which exports are available.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "directory": "<directory>"
    },
    "name": "list_exports"
  }
}

Input Schema

NameRequiredDescriptionDefault
directoryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A4.1/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and discloses error behavior (unparseable files return parse_error). It mentions return fields but does not address authorization or read-only nature. The disclosure is useful but could be more comprehensive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences with no waste: first sentence covers purpose and output, second sentence covers error handling and usage recommendation. Every sentence adds value, and the structure is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the main functionality, error case, and usage hint. An output schema exists, so return value details are not needed. For a simple list operation with one parameter, it is nearly complete, though additional context about directory path might help.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The only parameter 'directory' lacks any description in the schema (0% schema description coverage). The description mentions 'under NSMCP_ROOT' but does not clarify if it is relative or absolute, format, or valid values, leaving the agent with insufficient semantic guidance.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lists NetSuite saved-search exports under NSMCP_ROOT, specifies the return type (ExportSummary with fields), and distinguishes itself by recommending it as the first call when exports are unknown. This is a specific verb+resource with clear sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says 'Call this first when you don't already know which exports are available,' providing clear usage context. However, it does not explicitly state when not to use this tool or mention alternative sibling tools (e.g., query_export), but the guidance is still effective.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools