Skip to main content
Glama
JumenEngels

sap_analytics_cloud_mcp

by JumenEngels

sac_export_get_data

Retrieve data from any SAP Analytics Cloud provider entity set using OData queries, including filter, select, and pagination options. Supports distinct values and delta tracking.

Instructions

Generic: get data from any provider entity set. For Distinct queries use '{col}___Distinct'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
$topNoMax results
$skipNoSkip N
$countNoInclude count
$filterNoOData filter
$formatNoResponse format
$selectNoColumns
deltaidNoDelta ID
$orderbyNoOrder by
pagesizeNoPage size
providerYesProvider ID
delimiterNoCSV delimiter
entitySetYesEntity set name
namespaceYesNamespace ID
externalidNoExternal ID
trackChangesNoCreate subscription
Behavior2/5

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

No annotations; description only says 'get data' without mentioning side effects, permissions, rate limits, or any behavioral traits.

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 short sentences, front-loaded with purpose, efficient.

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?

High parameter count (15) and many siblings, but description is minimal. No output schema, no guidance on pagination or when to use generic vs. specific tools.

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 has 100% coverage, so description adds no value over schema. Baseline 3.

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?

Description states 'get data from any provider entity set', which is clear verb+resource. It distinguishes from sibling export tools by being generic, but doesn't explicitly differentiate from specific ones.

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 vs. siblings like sac_export_get_fact_data. Only a hint about distinct queries.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/JumenEngels/sap_analytics_cloud_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server