Skip to main content
Glama
julienchriqui-okkoer

netsuite-mcp-server

netsuite_create_expense_report

Create employee expense reports in NetSuite with line items for expense categories, amounts, currencies, and memos. Includes dry-run mode to preview the API request before submission.

Instructions

Create a new NetSuite expense report for an employee with expense lines. Required: employee, subsidiary, tranDate; per line: category (NS expense category ID), amount; multi-currency: currency. Optional: memo, externalId, expenseList.expense[].expenseDate, department, etc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
memoNo
dryRunNoIf true, return the NS request body without calling NS (debug mode)
currencyNoNS currency ID (1=EUR, 2=USD, 3=GBP). Default: '1' (EUR)
employeeYesEmployee internal ID
tranDateYesDate YYYY-MM-DD
externalIdNoIdempotency key
subsidiaryYesSubsidiary internal ID
expenseListNoExpense lines: { expense: [{ expenseDate, category, amount, memo, currency, department }] }
expenseListFormatNoDebug: A=array, B=expense.items, C=expenseList.items, D=expense.items like vendor bills (default). Use with dryRun to test.
Behavior2/5

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

No annotations are provided, so the description carries the full burden of disclosing behavioral traits. It mentions multi-currency and externalId as optional, but does not explain side effects, validation failure behavior, idempotency semantics, or return values. The description focuses on input requirements rather than what the tool does beyond creating a record, leaving the agent with limited insight into execution behavior.

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

Conciseness4/5

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

The description is concise and front-loaded with the primary purpose. It efficiently communicates required fields and optional ones in a single, dense sentence. The use of 'etc.' is vague and slightly undermines completeness, but overall it avoids unnecessary verbosity and earns its place.

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

Completeness3/5

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

The tool is complex (9 params, nested objects, no output schema), and the description covers the essential input structure but leaves gaps. It does not explain what the tool returns, the dryRun debug mode, or the expenseListFormat variants, which are present in the schema but omitted from the description. Without an output schema or annotations, the description should provide more context on outputs and error behavior, but it at least covers the core creation requirements.

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

Parameters4/5

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

Schema description coverage is high (89%), so the baseline is 3. The description adds value by explicitly highlighting required fields (employee, subsidiary, tranDate, category, amount) and the multi-currency condition for currency. It also gives a compact representation of the nested expenseList structure. While mostly redundant with schema, the multi-currency nuance and the summary of required per-line fields provide added semantic clarity.

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 action ('Create a new NetSuite expense report'), the target resource ('for an employee'), and the scope ('with expense lines'). It uses a specific verb and resource, and it is distinct from sibling tools like create_vendor_bill or create_journal_entry. This leaves no ambiguity about what the tool does.

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

Usage Guidelines3/5

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

The description implies usage by its verb 'Create' but provides no explicit guidance on when to choose this tool over alternatives. It does list required and optional parameters, which gives some context on prerequisites, but it does not state exclusions or alternative tool recommendations. The usage is inferred rather than explicitly stated.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/julienchriqui-okkoer/netsuite-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server