Skip to main content
Glama
Sign In
sap_analytics_cloud_mcp

sap_analytics_cloud_mcp

by JumenEngels
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

sac_users_list

List users in SAP Analytics Cloud with SCIM v2 filtering, pagination, and result limits.

Instructions

List users (SCIM v2).

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_users_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoMax results
filterNoSCIM filter
startIndexNo1-based start index

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior1/5

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

No annotations provided; the description is minimal and fails to disclose behavioral traits like pagination behavior, default result limits, response structure, or any side effects. For a listing tool, this misses critical information about how results are ordered or whether filters are applied server-side.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely brief (4 words) but lacks informative structure. It does not front-load key details or provide any context about the SCIM protocol expectations. Brevity compromises completeness.

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

Completeness2/5

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

Given no output schema and no annotations, the description is insufficient for an agent to understand the tool's behavior, especially regarding pagination, filtering capabilities, or the format of returned data. Sibling tools provide richer context but this tool lacks it.

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 three parameters. However, the description adds no additional meaning beyond the schema; it does not explain SCIM filter syntax or how 'count' and 'startIndex' interact for pagination.

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 the action (List) and resource (users) with a protocol reference (SCIM v2). It distinguishes from sibling tools like sac_users_create and sac_users_get by indicating a batch listing operation.

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?

No guidance on when to use this tool versus alternatives like sac_users_get for single users or sac_users_bulk for bulk operations. No mention of prerequisites or limitations such as maximum results or filtering constraints.

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