SAS MCP Server

Official

by sassoftware

Overview Schema Source Related Servers Discussions Admin

Python

Remote

Catalog Search

catalog_search

Read-onlyIdempotent

Search the SAS Data Governance catalog to find Viya assets like tables, columns, and reports by name, type, or metadata. Returns resource URIs and attributes for follow-up actions.

Instructions

Search the SAS Data Governance catalog for assets (tables, columns, reports, ...).

The catalog is a metadata index across the whole Viya environment, so this finds assets without needing to know their server/library first. Each hit includes the asset's resource_uri — the URI you can hand to the matching tool (e.g. get_report, get_castable_data) to act on the live asset — and an attributes map with whatever metadata the catalog holds for it (commonly library, rowCount, columnCount, completenessPercent, reviewStatus, informationPrivacy, and analysisTimeStamp).

The query uses the SAS catalog search grammar:

Free text matches names, with wildcards * (0+ chars) and ? (1 char): cust*.
Facets constrain fields, e.g. AssetType:Report, Name:sales, Library.name:PUBLIC, Column.informationPrivacy:Sensitive.
Ranges DateModified:[2024-01-01 TO 2024-12-31] and + to require a term. Combine freely: AssetType:"CAS Table" +Name:cust*. Use catalog_search_helper to discover valid facet names and values.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum hits to return (default 20).
`query`	Yes	The catalog search query (see grammar above). Use ``*`` to match all names.
`start`	No	Offset of the first hit (default 0).
`indices`	No	Comma-separated index name(s) to search (default 'catalog').	catalog

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.1/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds worthwhile context by specifying what each hit contains (resource_uri and attributes map with example keys), which goes beyond the annotations, but doesn't cover pagination behavior beyond element semantics.

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?

Front-loads purpose and environment scope, then details return shape and query grammar. The grammar section is appropriately detailed for a complex query language, though slightly long; every section earns its place.

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 a rich query grammar and follow-up actions to sibling tools, the description covers purpose, return shape, and grammar. Output schema exists, so return values need not be explained. Slightly missing explicit exclusion guidance, but otherwise complete for an agent to invoke correctly.

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%, so baseline is 3. The description adds substantial value by documenting the query grammar — wildcards, facets, ranges, the + operator, and combination syntax — which meaningfully exceeds what the schema's one-line description provides.

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?

States a specific verb (search) and resource (SAS Data Governance catalog assets) and names concrete asset types. It distinguishes itself from server/library-scoped siblings by explaining that the catalog is a metadata index across the whole environment, so assets can be found without knowing server/library first.

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

Usage Guidelines4/5

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

Explains what the tool is good for (finding assets without knowing server/library) and routes the agent to catalog_search_helper for facet discovery, plus get_report/get_castable_data for follow-up actions. It lacks explicit when-not-to-use guidance versus list-based tools like list_reports or list_castables, but provides clear context.

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

Deploy Server