Skip to main content
Glama
Sign In
singlestore-mcp-server

singlestore-mcp-server

by jonasliesas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

sas_libraries

Read-only

Retrieve SAS library metadata from a SAS Viya compute session, including engine, path, and SingleStore database details, using the active or saved connection.

Instructions

SAS libraries in the Workspace's SAS Compute session (compute context + startup code): engine, path and, for SAS/ACCESS to SingleStore (engine S2 / SSTORE), the SingleStore database. connection: a saved SAS Viya connection (default: the active one).

Input Schema

NameRequiredDescriptionDefault
refreshNo
connectionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.11.0
    • addedInput schema / properties / connection
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Connection"
+}
  2. Addedv0.10.1

TDQS

A3.7/5.0
Behavior3/5

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

The readOnlyHint annotation establishes that this is a safe read operation, while the description adds that results reflect the compute context and startup code and explains the connection default. It does not clarify what refresh changes, whether cached results are normally used, or whether invocation can start a Compute session and run startup code.

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 compact and front-loaded with the resource, session scope, and returned fields. The special S2/SSTORE handling and connection default add relevant information without filler or repetition.

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

Completeness3/5

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

For a simple two-parameter read tool, the description covers the main scope, notable output fields, and connection behavior sufficiently for a default invocation. The unexplained refresh flag and lack of explicit differentiation from closely related library tools remain material gaps, especially without an output schema.

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?

With 0% schema description coverage, the description usefully explains that connection selects a saved SAS Viya connection and defaults to the active one. However, refresh is entirely undocumented, leaving the agent unable to determine what true does or when it should be supplied.

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 identifies the resource and scope precisely: SAS libraries in the Workspace's SAS Compute session, including engine, path, and SingleStore database details for S2/SSTORE engines. Although it lacks an explicit verb such as "list," the Compute-session scope helps distinguish it from siblings such as sas9_libraries and cas_caslibs.

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?

The Workspace SAS Compute context and the option to select a saved SAS Viya connection provide clear usage context. It does not explicitly say when to prefer sas9_libraries, cas_caslibs, or another inspection tool, nor when refreshing is appropriate.

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