Skip to main content
Glama
ClementRingot

SAP Released Objects Server

by ClementRingot
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Get SAP Object Details

sap_get_object_details
Read-onlyIdempotent

Retrieve detailed release status and Clean Core Level for any SAP object by type and name, including successor information.

Instructions

Get detailed information about a specific SAP object by its exact type and name. Returns Clean Core Level, state, successor info, application component, and more. Use this to check if a specific object (table, class, CDS view...) is released for ABAP Cloud and what its Clean Core Level is.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
versionNoS/4HANA version for Private Cloud or On-Premise systems. Use 'latest' for the most recent version. Format: YEAR for base release, or YEAR_FPS where FPS is the Feature Pack Stack / SP number. IMPORTANT: '2022_1' = FPS01/SP01, '2023_3' = FPS03/SP03, etc. Always use the YEAR_N format when a specific SP/FPS is requested. Use sap_list_versions to see all currently available versions. Ignored for public_cloud and btp systems. Default: latest.latest
object_nameYesExact object name (e.g., 'MARA', 'CL_ABAP_UNIT_ASSERT', 'I_PRODUCT').
object_typeYesTADIR object type (e.g., 'TABL', 'CLAS', 'DDLS', 'DTEL', 'INTF', 'BDEF').
system_typeNoSAP system type. 'public_cloud' = S/4HANA Cloud Public Edition (Level A Released APIs only). 'btp' = BTP ABAP Environment / Steampunk (Level A Released APIs only, separate dataset from public_cloud). 'private_cloud' = S/4HANA Cloud Private Edition (Levels A-D, version-specific files available). 'on_premise' = S/4HANA on-premise (Levels A-D, version-specific files available). Default: public_cloud.public_cloud
clean_core_levelNoMaximum Clean Core Level to include in results (cumulative). Replaces the 3-tier extensibility model since August 2025. Level A: Released APIs only (ABAP Cloud, fully upgrade-safe). Level B: + Classic APIs (upgrade-stable, governance recommended). Level C: + Internal/unclassified objects (manageable risk, consult changelog). Level D: + noAPI objects (not Clean Core, should be remediated). For public_cloud and btp systems, only Level A is available. Default: A.A

Tool Definition Quality

A4.2/5.0
Behavior4/5

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

Annotations declare readOnly=true and destructive=false. Description adds behavioral context by specifying what is returned (Clean Core Level, state, successor info, etc.), complementing annotations without contradiction.

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 sentences, front-loaded with purpose and use case. No wasted words; every sentence is meaningful and concise.

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?

Given 5 parameters and no output schema, description sufficiently covers purpose, return fields, and usage context. It could benefit from explicitly listing all return fields, but 'and more' suffices. Annotations cover side effects.

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 detailed parameter descriptions. The tool description does not add significant parameter information beyond what the schema already provides, so baseline 3 is appropriate.

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?

Description clearly states it retrieves detailed information for a specific SAP object by type and name, listing returned fields. It distinguishes from siblings like sap_search_objects (searching) and sap_find_successor (finding successor).

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?

Description gives clear use case: checking if an object is released for ABAP Cloud. It explicitly references sap_list_versions for version info, providing an alternative. However, it does not explicitly state when not to use this tool vs. all siblings.

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/ClementRingot/ROSA'

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