Skip to main content
Glama
MarioDeFelipe

SAP Datasphere MCP Server

get_asset_by_compound_key

Use space ID and asset ID to directly retrieve asset metadata through OData compound key access.

Instructions

Retrieve asset using OData compound key identifier (alternative access method).

Use this tool when:

  • You have both space ID and asset ID ready

  • Want direct access without knowing the exact endpoint structure

  • Working with bookmarked or favorited assets

  • Have pre-known asset identifiers from other systems

  • Need to resolve cross-references quickly

What you'll get:

  • Same comprehensive metadata as get_asset_details

  • Complete asset information with consumption URLs

  • All dimensions, measures, and relationships

  • Technical and business context

Required parameters:

  • space_id: The space identifier

  • asset_id: The asset identifier

How it works: This tool combines space_id and asset_id into an OData compound key format: spaceId='SAP_CONTENT',assetId='SAP_SC_FI_AM_FINTRANSACTIONS'

Example queries:

  • "Get asset SAP_SC_FI_AM_FINTRANSACTIONS from SAP_CONTENT using compound key"

  • "Retrieve CUSTOMER_VIEW in SALES_SPACE"

When to use this vs get_asset_details:

  • Use this: When you want simplified parameter passing

  • Use get_asset_details: When you need expand options or prefer explicit endpoint

Note: This uses the Catalog API: GET /api/v1/datasphere/consumption/catalog/assets({compoundKey})

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
space_idYesThe space identifier in UPPERCASE (e.g., 'SAP_CONTENT', 'SALES_SPACE').
asset_idYesThe asset identifier (e.g., 'SAP_SC_FI_AM_FINTRANSACTIONS', 'CUSTOMER_VIEW').
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It explains the compound key format and underlying API call, but could mention idempotency or error scenarios for completeness.

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

Conciseness3/5

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

The description is thorough but lengthy with multiple sections. It could be more concise while retaining key information.

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

Completeness5/5

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

Given no output schema, the description adequately explains what is returned (same as get_asset_details, comprehensive metadata). It provides a complete picture for the tool's usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so parameters are already well-documented. The description adds value by showing the compound key format and providing examples, going beyond the schema.

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 it retrieves an asset using a compound key, and explicitly distinguishes it from the sibling tool 'get_asset_details' by noting it offers simplified parameter passing.

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

Usage Guidelines5/5

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

Provides explicit guidance on when to use (having space_id and asset_id, cross-references) and when to use the alternative 'get_asset_details' (for expand options). Includes example 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/MarioDeFelipe/sap-datasphere-mcp'

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