Skip to main content
Glama
marianfoo

SAP Documentation MCP Server

by marianfoo
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

abap_feature_matrix

Check ABAP feature availability across SAP releases. Find when a feature was introduced or compare releases.

Instructions

ABAP FEATURE MATRIX: abap_feature_matrix(query="feature keywords")

FUNCTION NAME: abap_feature_matrix

Search the Software Heroes ABAP Feature Matrix to check feature availability across SAP releases. The matrix shows which ABAP features are available in different SAP releases (7.40, 7.50, 7.52, 7.54, 7.55, 7.56, 7.57, 2020, 2021, 2022, 2023, LATEST).

DATA SOURCE: https://software-heroes.com/en/abap-feature-matrix Full matrix is fetched in English and cached for 24 hours. Filtering is done locally.

STATUS MARKERS: • ✅ available - Feature is available in the release • ❌ unavailable - Feature is not available • ⭕ deprecated - Feature is deprecated • ❔ needs_review - Status needs verification • 🔽 downport - Feature was backported from a newer release

PARAMETERS: • query (optional): Feature keywords to search for (e.g., "inline declaration", "CORRESPONDING", "mesh"). If empty, returns all features. • limit (optional): Maximum number of results. If not specified, returns all matching features.

RETURNS JSON with: • matches: Array of matching features with:

  • feature: Feature name

  • section: Category (e.g., "ABAP SQL", "ABAP Statements")

  • link: URL to more information (if available)

  • statusByRelease: Object mapping release versions to status

  • score: Relevance score • meta: Matrix metadata (totalFeatures, totalSections, sections) • sourceUrl: Attribution URL to Software Heroes • legend: Explanation of status markers

EXAMPLES: abap_feature_matrix(query="inline declaration") abap_feature_matrix(query="CORRESPONDING") abap_feature_matrix() - returns all features abap_feature_matrix(query="CDS", limit=10)

USE CASES: • Check if a feature is available in your target SAP release • Find when a specific ABAP feature was introduced • Compare feature availability across releases • Get full matrix and let LLM interpret/filter results

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoFeature keywords to search for, in ENGLISH (matrix is English). If empty or not provided, returns all features.
limitNoMaximum number of results. If not specified, returns all matching features.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
matchesYes
metaYes
sourceUrlYes
legendYes

Tool Definition Quality

A4.5/5.0
Behavior4/5

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

With no annotations provided, the description fully carries the burden. It discloses the data source, caching behavior (24-hour cache), local filtering, and status markers. It also describes the return structure with JSON fields. No destructive or auth-related information is needed as it is a read-only query tool.

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?

The description is well-structured with clear sections (FUNCTION NAME, DESCRIPTION, DATA SOURCE, STATUS MARKERS, PARAMETERS, RETURNS, EXAMPLES, USE CASES). It is somewhat verbose but every section adds value. The key purpose is front-loaded in the first line.

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 the tool's low complexity (2 optional parameters, no required params, output schema present), the description is complete. It explains all possible behaviors, return fields, status meanings, and provides multiple usage examples. An agent can use this tool without ambiguity.

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

Parameters5/5

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

Schema coverage is 100% (both query and limit are defined). The description adds significant value: it clarifies query expects English keywords, provides concrete examples (inline declaration, CORRESPONDING, CDS), shows how to use limit with an example, and demonstrates empty query behavior. This greatly aids correct parameter usage.

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 explicitly states it searches the ABAP Feature Matrix to check feature availability across SAP releases. It clearly distinguishes itself from sibling tools that search SAP community or discovery center, making the purpose unambiguous.

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 'USE CASES' section lists four specific scenarios for when to use this tool (check feature availability, find introduction, compare releases, get full matrix). While it doesn't explicitly state when not to use or mention alternatives, the scenarios are clear and comprehensive.

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