Skip to main content
Glama
sassoftware

SAS MCP Server

Official
by sassoftware

List Glossary Terms

list_glossary_terms
Read-onlyIdempotent

Filter glossary terms by parent, term type, name substring, or custom attributes. Use pagination to browse the full SAS glossary hierarchy.

Instructions

List glossary terms by structure — term type, parent, or name fragment.

The counterpart to search_glossary_terms: exact filters instead of ranked text. Use it to walk the hierarchy (parent_id returns a term's direct children, which is the authoritative parent/child relationship), to inventory one term type, or to page the whole dictionary with no arguments at all.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum terms to return (default 20).
startNoOffset of the first term (default 0).
parent_idNoReturn only the direct children of this term id.
term_typeNoRestrict to one term type — its UUID or its name.
name_containsNoSubstring match on the term name.
include_draftsNoInclude unpublished drafts (default false — published only).
attribute_filterNoKeep only terms whose attributes match, e.g. ``{"Needs masking": true}`` or ``{"Regions": "EMEA"}``. Clauses are ANDed; a multi-select matches when it *contains* the value. **The glossary cannot filter on attributes server-side**, so this is applied here over pages fetched for the purpose: the result reports how many terms were scanned and whether the scan reached the end. Narrow it with ``term_type`` or ``parent_id`` where you can.
include_attributesNoAlso return each term's custom attributes, named (default false). Free — the listing already carries them.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.14.0

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/destructive annotations, the description reveals that attribute filtering is client-side over fetched pages, reports scanned count and scan completion, and that parent_id gives the authoritative parent/child relationship. This is exactly the kind of non-obvious behavior an agent needs.

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?

Two compact paragraphs, front-loaded with the main purpose, followed by routing guidance and a caveat. Every sentence earns its place, and there is no repetition of schema or annotation content.

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?

Combined with the fully documented input schema, output schema, and annotations, the description covers purpose, usage, and behavioral caveats. Nothing an agent needs to correctly invoke this read-only list tool is missing.

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?

All 8 parameters already have clear schema descriptions, so the baseline is 3. The description adds valuable semantics for key parameters, especially the client-side attribute_filter behavior and the authoritative parent_id relationship, justifying one point above baseline.

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 opens with a specific verb and resource, 'List glossary terms by structure — term type, parent, or name fragment,' which immediately conveys what the tool does. It also explicitly distinguishes it from search_glossary_terms, making the purpose unmistakable.

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?

The description names search_glossary_terms as the counterpart and states the selection principle: exact filters instead of ranked text. It lists concrete use cases — walking the hierarchy via parent_id, inventorying a term type, and paging the full dictionary — so an agent knows exactly when to choose this tool.

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