Skip to main content
Glama
Sign In
SAS MCP Server

SAS MCP Server

Official
by sassoftware
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

List Model Projects

list_model_projects
Read-onlyIdempotent

Retrieve SAS Model Manager projects, ordered by most recent changes, with optional filters for repository and project name and a limit on results.

Instructions

List SAS Model Manager projects, most recently changed first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_model_projects"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum projects (default 50).
repositoryNoOnly this repository (name or ID); all when omitted.
name_filterNoOnly projects whose name contains this text.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.19.2

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds one genuine fact beyond that — results are ordered most-recently-changed first — but says nothing about pagination, truncation at the default limit, or total counts.

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 eleven-word sentence with zero filler, front-loading the resource and appending the sort order where it belongs. Nothing is redundant and nothing needs reordering.

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?

For a simple, fully annotated, non-destructive list tool with a complete input schema and an output schema, the description covers what it does and how results are ordered. The main residual gap is disambiguation from 'list_ml_projects', which matters given how similar the names are.

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 each of the three optional parameters (limit, repository, name_filter) is documented in the schema with defaults, so the description does not need to repeat them. It adds no extra meaning such as case sensitivity of name_filter or whether repository accepts both name and ID, leaving this at the schema baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('List') plus a specific resource ('SAS Model Manager projects'), which is more precise than a generic 'list projects'. However it never distinguishes itself from the sibling 'list_ml_projects', leaving an agent to infer which project type it wants from the SAS/Model Manager qualifier alone.

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?

There is no when-to-use guidance, no prerequisites, and no mention of the closely named alternative 'list_ml_projects'. The ordering hint ('most recently changed first') is a behavioral fact, not usage guidance, so the agent gets no routing help.

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

Deploy Server

Other Tools