Skip to main content
Glama
marianfoo

SAP Documentation MCP Server

sap_search_objects

Search SAP released objects to find APIs and check clean core compliance. Filter by system type, clean core level, object type, or application component.

Instructions

SEARCH SAP RELEASED OBJECTS: sap_search_objects(query="CL_ABAP_REGEX")

Search SAP released objects from the official SAP API Release State repository (SAP/abap-atc-cr-cv-s4hc).

Use this tool when you need to: • Find which SAP objects (classes, interfaces, tables, CDS views, function groups, BAdIs, etc.) are available and released for a given topic or application area • Discover released APIs in a specific application component (e.g., MM-PUR, FI-GL, SD-SLS) • Browse what objects exist in a system type (S/4HANA Cloud Public, BTP ABAP, Private Cloud) • Filter by Clean Core compliance level: A=Released APIs only, B=includes Classic APIs, C=includes internal/stable, D=all objects • Find alternative released objects when looking for functionality in a specific domain

Do NOT use this for documentation content, code examples, or general SAP help — use the search tool for those. Use this specifically for API release status and clean core compliance discovery.

PARAMETERS: • query (optional): Object name or keyword to search (e.g. "CL_ABAP_REGEX", "purchase order", "MM") • system_type (optional, default: "public_cloud"): "public_cloud" | "btp" | "private_cloud" | "on_premise" • clean_core_level (optional, default: "A"): "A" | "B" | "C" | "D" — cumulative: B includes A+B, C includes A+B+C • object_type (optional): TADIR type filter, e.g. "CLAS", "INTF", "TABL", "DDLS" • app_component (optional): Application component prefix, e.g. "MM-PUR", "FI-GL" • state (optional): "released" | "deprecated" | "classicAPI" | "stable" | "notToBeReleased" | "noAPI" • limit (optional, default: 25, max: 100): Number of results per page • offset (optional, default: 0): Pagination offset

RETURNS (JSON with): • objects: Array of SAP objects with objectType, objectName, state, cleanCoreLevel, applicationComponent, softwareComponent • total: Total matching count • hasMore: Whether more results exist • nextOffset: Offset to use for next page

[PRE-LOADED CONTEXT] Context loading — data will be available on first use.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoObject name or topic keyword to search, in ENGLISH.
system_typeNoTarget SAP system type. Default: public_cloud.public_cloud
clean_core_levelNoMaximum Clean Core level to include. A=Released only, B=+Classic, C=+Internal, D=all. Default: A.A
object_typeNoTADIR object type filter, e.g. CLAS, INTF, TABL, DDLS, FUGR, BDEF, SRVD.
app_componentNoApplication component prefix, e.g. MM-PUR, FI-GL, SD-SLS.
stateNoFilter by release state.
limitNoResults per page. Default: 25. Max: 100.
offsetNoPagination offset. Default: 0.
Behavior4/5

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

No annotations present, but description covers the behavior well: searches an official repository, filters by Clean Core level and system type. Could explicitly state read-only nature for full transparency.

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

Conciseness4/5

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

Well-structured with bullet points and a clear example; front-loads the main purpose. Slightly verbose but justified by complexity of the tool.

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?

Despite no output schema, description details return structure (objects, total, hasMore, nextOffset). All 8 optional parameters are explained with sensible defaults and constraints.

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 baseline is 3. Description adds value with examples like 'query="CL_ABAP_REGEX"' and clarifies filter semantics (e.g., cumulative Clean Core levels). Exceeds baseline.

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 'Search SAP released objects' and provides concrete examples and use cases. It distinguishes from siblings like 'sap_get_object_details' and the general 'search' tool.

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 'Use this when' and 'Do NOT use this for' sections with named alternatives (e.g., 'search' tool for documentation). Clearly guides when to choose this tool over 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/marianfoo/mcp-sap-docs'

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