AgentTools.<tool>(tool_name="...", ...) or agent.add_tool.<tool>(tool_name="...", ...). Every tool requires a unique tool_name=. Each entry lists the tool’s configuration parameters. See the Agent reference for attaching and running tools.
agent — Agent
code_interpreter — Code Interpreter
Execute Python code in a sandboxed environment with file I/O support. Supports spreadsheet analysis, data visualization, and generating artifacts. To read or edit uploaded files, pass them in the files input as an actual array of file references; those files are mounted at /work/inputs/{filename} (curly braces shown for clarity; replace with the exact filename). Continued sessions restore prior inputs and generated files, so work can resume even if Python memory reset. Save output files to /work/outputs/ to have them collected as artifacts; call save_file(…) for durable/versioned user-visible files. Example: files=[“$history.69dd11a49033ae4d8e65ab33”] and pd.read_csv(‘/work/inputs/data.csv’); plt.savefig(‘/work/outputs/chart.png’). You will see stdout and stderr outputs after each execution step. Include an existing session id to keep executing code within the same session.
Platform docs: Code Interpreter
Optional files to make available to the code (e.g., spreadsheets, CSV files). Pass an actual array of file references, such as [“history.69dd11a49033ae4d8e65ab33"] or ["object.knowledge_base_item.6875a39904d4beff85bdde61”]. Files passed here are mounted into /work/inputs/<exact filename>; continued sessions also restore prior session files.
create_skill — Create Skill
Create a new skill with a name, description, and content
The full content/instructions of the skill. Use markdown formatting: headings (##, ###) to organize sections, bullet points (- or *) for instructions and guidelines, numbered lists (1. 2. 3.) for sequential steps, bold for key terms and critical instructions, and
code for technical terms or placeholders. Add a <br> tag between major sections for visual spacing.custom_tool — OpenAI-native built-ins (code_interpreter, file_search)
OpenAI-native built-ins (code_interpreter, file_search)
generate_chart — Generate Chart
Use this to generate a chart from. Convert a tabular file, dataframe or table to a chart or graph visualization. Supports bar, line, pie, scatter, and donut charts/graphs.
The type of chart to generate (bar, line, pie, scatter, donut)
One of:
bar, donut, line, pie, scatter, time_seriesThe dataframe to visualize as a chart. In case of csv, the input should be a properly formatted valid csv string with appropriate headers. When chaining from a tool that returned a CSV file (e.g. fetch_ratios.table), set dataframe_type=“file” and pass $action.<id>.table — never paste the upstream formatted_text/XML here.
Actual column names from the dataframe. It should be a string representing the comma separated list of column names.
The column name to use for the X-axis (categories). Must EXACTLY match (case-sensitive) one of the column names from the CSV header.
Column name(s) for Y-axis values. Must EXACTLY match (case-sensitive) column name(s) from the CSV header. For multi-series charts (multiple lines/bars), use comma-separated names like ‘revenue,profit,cost’.
Comma-separated icon URLs for each series (company logos, game art, product images, etc.), in same order as y_axis_fields. Leave empty for no icons.
Comma-separated display names for each Y-axis field, in same order as y_axis_fields (e.g. ‘MSFT,NVDA’ for tickers, ‘Halo,Fortnite’ for games, ‘US,EU,APAC’ for regions).
get_skill — Get Skill
Retrieve the full content of a skill by its ID
knowledge_base — Knowledge Base Reader
Semantically query a knowledge base that can contain files, scraped URLs, and data from synced integrations (e.g., Google Drive).
Platform docs: Knowledge Base Reader
The unit of retrieval. Chunks will return the most relevant chunks from the knowledge base as well as their text content. Documents will return the document metadata as well as most relevant snippets from the document. Pages will return complete pages with all chunks from pages containing relevant content
One of:
chunks, documents, pagesThe query will be used to search documents for relevant content semantically. Must not be empty, only include relevant information for retrieval or metadata filter generation. Generally expand any specific acronyms or abbreviations but include the original acronym or abbreviation as well
Extract separate questions from the query and retrieve content separately for each question to improve search performance
Use an LLM to generate metadata filters to refine your query. Agents should usually leave this false and provide filters directly in the filter input.
knowledge_base_agent — Knowledge Base Agent
Query a knowledge base using an agentic approach with tools.
Platform docs: Knowledge Base Agent
Optional additional context to help the agent understand the query better (e.g., conversation history, user preferences)
Select an existing knowledge base. You must provide the id in $.object.knowledge_base.id format
The natural language query. The agent will use this to determine the best way to query the knowledge base. Include the key criteria needed to answer the query.
Controls the query effort: ‘fast’ for quick answers, ‘focused’ for balanced depth, ‘deep’ for thorough analysis
knowledge_base_create — Create Knowledge Base
Dynamically create a Knowledge Base with configured options
Platform docs: Create Knowledge Base
The embedding model to use for the knowledge base. Format: provider/model
The method to break text into units before chunking. ‘words’: splits by word; ‘sentences’: splits by sentence boundary; ‘paragraphs’: splits by blank line/paragraph.
Strategy for grouping segmented text into final chunks. ‘sentence’: groups sentences; ‘markdown’: respects Markdown structure (headers, code); ‘dynamic’: optimizes breaks for size using chosen segmentation method.
knowledge_base_fetch_document_content — Knowledge Base Fetch Document Content
Fetch the full content of a specific document from a knowledge base by scrolling through all its chunks
Platform docs: Knowledge Base Fetch Document Content
Select an existing knowledge base
knowledge_base_fetch_items — Knowledge Base Fetch Items
Advanced knowledge base item fetching with traversal, filtering, and output shaping capabilities
Platform docs: Knowledge Base Fetch Items
JSON filter object, example filter syntax: ’{“type”: “condition”, “field”: “file_extension”, “operator”: “eq”, “value”: “pdf”}’ or ’{“type”: “condition”, “field”: “title”, “operator”: “match”, “value”: “Pantheon”}’ only use filters if explicitly requested by the user. Do not use filters on fields other than file type. Available operators include are eq and neq, do not use filter operator contains
Maximum depth for descendants traversal, use 0 to traverse up as deep as possible to get to {{limit}} items, use 1 to get direct children etc
Output verbosity level: metadata (no summaries), short (short summaries), or long (short and long summaries), Use metadata for for simply finding folders/ documents, use short for understanding folder/document contents, use long with a lower limit for deep understanding of a particular folder/subfolder
knowledge_base_get_item_bboxes — Knowledge Base Get Item Bboxes
Fetch OCR bounding boxes for specific pages of a PDF document in a knowledge base
knowledge_base_loader — Knowledge Base Loader
Load data into an existing knowledge base.
Platform docs: Knowledge Base Loader
The file to be added to the selected knowledge base. Note: to convert text to file, use the Text to File node
list_objects — List Objects
List VectorShift objects accessible to the current user
Include objects shared with you by other users
mcp_connector — Integration-backed MCP (Slack, GitHub, etc.)
Integration-backed MCP (Slack, GitHub, etc.)
mcp_server — Mcp Server
Bind an MCP server (created via web UI) as a tool source
pipeline — Pipeline
Platform docs: Pipeline
read_memory — Read Memory
Load the full content of a memory entry. Use this when: - A memory shown in context appears truncated or abbreviated - A knowledge base memory needs its full document index (folder structure, document list) - You need the complete text of a memory that shows [content not loaded] Returns the full content as a string. Knowledge base memories: returns the KB’s document index and folder hierarchy (not document content). Use knowledge_base_query to search document content.
transformation — Transformation
Use Python code to create a custom node
Platform docs: Transformation
The ID of the transformation to be used
write_memory — Write Memory
Create or update a Memory object for use with context-aware agents. You can store text memory content and or references to object types like knowledge bases, knowledge base items, files and prompts.
Content to store in the memory. Each item can be plain text or an object reference using ‘object.knowledge_base.617’, ‘$object.file.718’). Allowed object types: KnowledgeBase, File, KnowledgeBaseItem, Prompt.
Optional explicit user ID to use for User scope. If empty, authenticated caller user ID is used. Provide the raw ObjectId only (e.g. ‘6875a39904d4beff85bdde61’), not prefixed with ‘user:’ or any other label.
