mynt

module function · N/llm

createTool()

llm.createTool(options)

Creates a tool the LLM can request.

Implementation
Not started
Design
Open for proposals suggest how it should read
Proposals
A suitescript api
Signature
llm.createTool(options)
Module
N/llm
Returns
llm.Tool
Governance
None
Script types
Server scripts
Version
SuiteScript 2.x, documented for 2.1; since NetSuite 2025.2
call shapefrom Oracle's parameter table
1llm.createTool({2    name: /* string, required */3});
Oracle reference for this method
ParameterTypeRequiredDescription
options.namestringrequiredA unique identifier for the tool. This parameter is used when the LLM refers to this tool in tool call requests (which are represented as llm.ToolCall objects).
B mynt syntax

No Mynt syntax yet.

Nothing in the language compiles to llm.createTool(options) today. How should it read?

C community proposals

Competing syntax for createTool, from GitHub Discussions. Select two or more to compare them side by side.

All discussions

Loading proposals from GitHub…

D suggest an alternative

Write the Mynt you wish you could write.

A good proposal shows the syntax, the SuiteScript it should become, and argues for it: why it is clearer, how it fits the rest of the language, what it makes harder.

  • Clarity. Does it say what happens, without ceremony?
  • Consistency. Does it read like load, save and Ref[field]?
  • Expressiveness. Does it cover the cases people actually write?
  • Honesty. Does it hide a NetSuite cost, such as governance, that a reader should see?

N/llm · llm.createTool(options)

Suggest syntax for createTool