SAS MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

Upload Inline Data

upload_inline_data

Turn small inline CSV or TSV text into a CAS table for quick lookup or test data. For larger or binary files, upload the file instead.

Instructions

Create a small CAS table from inline delimited text passed as a string.

Use this only for tiny, hand-built tables — a lookup/mapping table the model constructs on the fly, or a quick test table — because the whole payload travels through the model's context as a tool argument. For anything larger, or any file you already have, use upload_data (file_path/url), which reads the bytes server-side instead.

Text formats only: csv (default) or tsv (tab-separated). For binary formats (Excel, sas7bdat, sashdat) use upload_data.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes	The delimited text, including the header row.
`server_id`	Yes	CAS server name or ID.
`table_name`	Yes	Name for the new table.
`caslib_name`	Yes	Target caslib name.
`data_format`	No	'csv' (default) or 'tsv' (alias 'tab').	csv
`contains_header_row`	No	Whether the first row holds column names (default True).

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.2.1Jul 4, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations carry only generic false hints, so the description adds meaningful behavior: creation, the context-payload cost of inline data, and the server-side alternative for upload_data. It does not discuss overwrite or idempotency behavior in detail, but idempotentHint=false and the create semantics partly cover that.

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 front-loaded with the core action, then uses two short paragraphs for usage boundaries and format constraints. Every sentence earns its place; no filler or repetition of schema.

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

Completeness5/5

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

For a straightforward create-from-string tool with a fully documented 6-parameter schema and output schema present, the description supplies enough context to invoke it correctly and avoid the wrong sibling. No important operational gap remains.

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

Parameters3/5

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

Schema description coverage is 100%, and the description does not need to restate parameters. It adds minor context about csv/tsv text formats and inline string payload, but parameter-level meaning is already fully documented in the schema.

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?

First sentence states a specific action and resource: 'Create a small CAS table from inline delimited text passed as a string.' The note that this is for tiny hand-built tables and mentions upload_data as the file-based counterpart clearly distinguishes it from sibling tools.

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?

Description explicitly scopes usage: use only for tiny hand-built tables, and directs larger/file cases to upload_data, which reads bytes server-side. It also states text formats only and directs binary formats to upload_data.

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

Deploy Server