Skip to main content
Glama
Sign In
mcp-sac-tools

mcp-sac-tools

by pmankineni
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

sac_list_users

List users in the SAP Analytics Cloud tenant with SCIM filtering and pagination support.

Instructions

List users in the SAC tenant. Supports SCIM filtering (e.g. filter='userName eq "john"').

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": "sac_list_users"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoNumber of results per page
filterNoSCIM filter expression
startIndexNo1-based start index for paging

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations provided. The mention of SCIM filtering adds some behavioral context, but the description does not disclose pagination behavior (count, startIndex) or any side effects, leaving gaps in transparency.

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?

Extremely concise at two sentences, front-loaded with the core purpose and then a key feature (SCIM filtering). Every sentence adds value.

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?

Core purpose and filtering are clear, but the description omits pagination behavior (count, startIndex) and response details. For a list tool with no output schema, slightly more context would improve completeness.

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% with descriptions for all parameters. The description confirms the SCIM filter usage but adds no new meaning beyond what the schema already provides for count and startIndex.

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 'List users' with a specific resource (SAC tenant) and includes SCIM filtering support, distinguishing it from related tools like sac_get_user or sac_create_user.

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

Usage Guidelines3/5

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

No explicit guidance on when to use this vs. alternatives (e.g., sac_get_user for single user). The description implies usage for listing with optional filtering but lacks exclusion criteria.

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