Skip to main content
Glama
sassoftware

SAS MCP Server

Official
by sassoftware

create_ml_project

Create an AutoML pipeline automation project by specifying a project name, training data table URI, and target variable. Optionally set prediction type, target event level, and auto-run pipelines.

Instructions

Create a new AutoML pipeline automation project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_nameYesName for the project.
data_table_uriYesURI of the training data table (e.g. '/dataTables/dataSources/cas~fs~cas-shared-default~fs~Public/tables/HMEQ').
target_variableYesName of the target/response variable.
descriptionNoOptional project description.
prediction_typeNo'binary', 'interval', or 'nominal' (default 'binary').binary
target_event_levelNoTarget event level for binary/nominal classification (default '1').1
auto_runNoWhether to automatically run pipelines after creation (default True).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations provided, so the description carries full burden. It fails to disclose side effects, prerequisites, or behavioral traits beyond the schema (e.g., permissions needed, state changes).

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?

A single, clear sentence with no redundant information. Every word serves a purpose.

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

Completeness2/5

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

Given 7 parameters and a long sibling list, the description lacks context about what an AutoML pipeline project entails and how it relates to other tools. Incomplete for effective selection.

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 coverage is 100%, so the schema already explains all parameters. The description adds no extra meaning beyond the tool's main purpose. Baseline 3 is appropriate.

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') and the resource ('AutoML pipeline automation project'), which is distinct from sibling tools like run_ml_project or list_ml_projects.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives; no conditions or exclusions are mentioned. The description does not help the agent decide context.

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