Skip to main content
Glama
Sign In
SAP Datasphere MCP Server

SAP Datasphere MCP Server

by DimiDR
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_analytical_datasets

List analytical datasets within a specific asset to discover queryable models for business intelligence and reporting. Returns entity set names, types, and URLs for data access.

Instructions

List all available analytical datasets within a specific asset. Discovers analytical models that can be queried for business intelligence and reporting. Returns entity sets with their names, types, and URLs for data access.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "space_id": "<space_id>",
      "asset_id": "<asset_id>"
    },
    "name": "list_analytical_datasets"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNoMaximum number of datasets to return (default: 50, max: 1000)
skipNoNumber of datasets to skip for pagination
asset_idYesAsset identifier (e.g., 'SAP_SC_FI_AM_FINTRANSACTIONS')
space_idYesSpace identifier (e.g., 'SAP_CONTENT')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the full transparency burden. It correctly frames the operation as a read-only listing and explicitly states what is returned, which is the most important behavioral trait. It doesn't mention auth or side effects, but for a list operation this is reasonably sufficient.

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?

Three sentences, front-loaded with the core verb and object, and every sentence adds useful information about purpose, scope, or return value. There is no wasted verbiage.

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

Completeness4/5

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

For a paginated list tool with no output schema, the description adequately covers what the tool does, its scope, and what it returns. It doesn't need to repeat schema details, and the overall context is sufficient for an agent to select it appropriately.

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?

The input schema already covers all four parameters with descriptions, examples, and defaults, so the description adds no additional parameter semantics. This matches the baseline score of 3 when schema coverage is high.

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 ('List') and a specific resource ('analytical datasets within a specific asset'), clearly distinguishing this discovery tool from query-oriented or metadata-only siblings. It also names the expected return content (entity sets, names, types, URLs), 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 Guidelines4/5

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

The description clearly frames when to use the tool: to discover analytical datasets/models that can later be queried for business intelligence. It does not explicitly name alternative tools or exclusion criteria, but the 'can be queried' phrasing implies this is the discovery step, so the usage context is clear.

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