Skip to main content
Glama
sassoftware

SAS MCP Server

Official
by sassoftware

upload_data

Upload a data file into a CAS table by providing a file path or URL. The server reads the file and creates the table.

Instructions

Upload a data file into a CAS table — read by the server, not the model.

Provide the data by reference through exactly one of:

  • file_path — the server reads the file off its own disk (in stdio mode that's your machine). Disable with ALLOW_LOCAL_FILE_UPLOAD=false.

  • url — the server fetches it over HTTP.

Either way the bytes are read server-side and never pass through the calling model's context window. To create a small table you are building inline (no file or URL), use the upload_inline_data tool instead.

The casManagement uploadTable endpoint only accepts an uploaded file (multipart form-data) and has no URL parameter, so url is fetched and sent on as the multipart file part.

Formats. Per the uploadTable API: csv, xls, xlsx (single sheet), sas7bdat, sashdat; tsv is csv with a tab delimiter. parquet is not accepted and is rejected up front with guidance (load via a path-based caslib + promote_table_to_memory, or convert to csv/sas7bdat). The format is auto-detected from the file_path/url extension; pass data_format to override (needed for URLs with no clean suffix).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoHTTP(S) URL the server fetches the file from.
file_pathNoPath to a data file the server reads directly from disk.
server_idYesCAS server name or ID.
sheet_nameNoFor Excel sources, the worksheet to import (first sheet by default).
table_nameYesName for the new table.
caslib_nameYesTarget caslib name.
data_formatNoOverride format detection. One of csv, tsv, xls, xlsx, sas7bdat, sashdat (aliases: excel→xlsx, tab→tsv, sas→sas7bdat).
contains_header_rowNoWhether the first row holds column names — applies to csv/tsv/Excel (default True).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations provided, so description carries full burden. It discloses that bytes are read server-side and never pass through the model's context window, that file_path can be disabled via env variable, that url is fetched and sent as multipart, and that format detection is automatic. However, it does not mention whether existing tables are overwritten or any error handling details.

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 well-structured with a clear opening, a bulleted list of data source options, and a paragraph on formats. Each sentence adds value, though it could be slightly more concise. Overall well-organized for an experienced user.

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?

Given 8 parameters, 100% schema coverage, and an output schema (not shown), the description covers data flow, parameter interactions, format restrictions, and rejections. It lacks details about output or concurrency, but for a data upload tool, it is fairly complete.

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 coverage is 100%, baseline 3. Description adds significant context: explains the mutually exclusive constraint between file_path and url, lists accepted format aliases, and clarifies the behavior of sheet_name and contains_header_row. It also explains how data_format overrides detection.

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 uploads a data file into a CAS table, with server-side reading. It distinguishes from upload_inline_data (for inline tables) and upload_file (likely for non-CAS). The verb 'upload' and resource 'data file into CAS table' are specific.

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

Usage Guidelines5/5

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

Explicitly says when to use this tool (upload a data file to CAS) and when not (use upload_inline_data for small inline tables). Provides guidance on format restrictions (parquet rejected with alternative) and the two data source options (file_path or url). Clear context and exclusions.

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/sassoftware/sas-mcp-server'

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