Skip to main content
Glama
marianfoo

SAP Documentation MCP Server

by marianfoo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

sap_search_objects

Search SAP released objects by topic, system type, or app component to find Clean Core-compliant APIs and alternatives for development.

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 modules, 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): Actual or TADIR type, e.g. "FUNC", "BADI_DEF", "CDS_STOB", "CLAS", "DDLS", "FUGR" • 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 containing:

  • objectType, objectName: Actual identity (TADIR identity for legacy records)

  • tadirObject, tadirObjName: Original TADIR container when available; also searchable

  • 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
limitNoResults per page. Default: 25. Max: 100.
queryNoObject name or topic keyword to search, in ENGLISH.
stateNoFilter by release state.
offsetNoPagination offset. Default: 0.
object_typeNoActual or TADIR object type filter, e.g. FUNC, BADI_DEF, CDS_STOB, CLAS, DDLS, FUGR.
system_typeNoTarget SAP system type. Default: public_cloud.public_cloud
app_componentNoApplication component prefix, e.g. MM-PUR, FI-GL, SD-SLS.
clean_core_levelNoMaximum Clean Core level to include. A=Released only, B=+Classic, C=+Internal, D=all. Default: A.A

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.57
    • changedInput schema / properties / object_type / description
      Previous value: -"TADIR object type filter, e.g. CLAS, INTF, TABL, DDLS, FUGR, BDEF, SRVD."New value: +"Actual or TADIR object type filter, e.g. FUNC, BADI_DEF, CDS_STOB, CLAS, DDLS, FUGR."
  2. Addedv0.3.50

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and largely succeeds: it names the data source, discloses the return shape (objects/total/hasMore/nextOffset) and pagination, and explains the cumulative nature of clean_core_level. It omits auth/permission requirements and rate limits, which keeps it short of a 5.

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?

Front-loaded with the intent and a usage/anti-usage section, which is efficient for an agent scanning for routing. The trailing parameter enumeration duplicates structured schema data and is the one part that does not fully earn its space.

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 an 8-parameter filter tool with no output schema, the description compensates by documenting the return object, pagination fields, the data source, and the semantics of the trickier filters. It is largely complete, with only operational details (auth, freshness of release data) left unstated.

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 description coverage is 100%, so the schema already documents all eight parameters. The description's parameter block largely restates the schema (query examples, defaults, enums), and the cumulative clean-core note adds only marginal meaning over the schema's 'A=Released only ... D=all'. Baseline 3 applies.

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?

States a specific verb+resource+scope: searching SAP released objects from the official SAP API Release State repository. It explicitly names the sibling it is not for (use `search` for docs/code/help), so an agent can separate it from the other search tools without opening a schema.

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 an explicit bulleted list of when-to-use scenarios (topic discovery, application component lookup, system-type browsing, clean-core filtering) plus a negative instruction routing documentation queries to the `search` tool. Both the selecting condition and the alternative are stated.

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