Skip to main content
Glama
marianfoo

SAP Documentation MCP Server

by marianfoo
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

sap_discovery_center_search

Find SAP BTP services by keyword, category, or license model using the SAP Discovery Center search. Discover solutions for AI, integration, database, and more.

Instructions

SEARCH SAP BTP SERVICES: sap_discovery_center_search(query="SAP Build")

FUNCTION NAME: sap_discovery_center_search

Search the SAP Discovery Center service catalog to find SAP Business Technology Platform (BTP) services, solutions, and capabilities.

Use this tool when you need to:

  • Find which SAP BTP services are available for a specific use case (e.g., integration, AI, database, extension development)

  • Discover services by name or keyword (e.g., "HANA", "Integration Suite", "Build", "AI Core")

  • Browse services filtered by license model (free tier, pay-as-you-go, subscription)

  • Find deprecated BTP services and their replacements

  • Explore SAP AI and machine learning services on BTP

  • Compare BTP services within a category

Do NOT use this for ABAP documentation, code examples, or SAP Help content – use the 'search' tool for those. After finding a service, use sap_discovery_center_service(serviceId="...") to get full details including pricing, roadmap, and documentation links.

PARAMETERS: • query (required): Search terms for BTP services. Use service names or capability keywords. • top (optional, default 10, max 25): Number of results to return. • category (optional): Filter by category, e.g., "AI", "Integration", "Data and Analytics", "Application Development and Automation", "Foundation / Cross Services". • license_model (optional): Filter by license type: "free", "payg", "subscription", "btpea", "cloudcredits".

RETURNS (JSON): • services[]: Array of matching services with id, name, shortName, description, category, additionalCategories, licenseModelType, provider, tags, ribbon, isDeprecated • total: Number of results returned

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch terms for BTP services, in ENGLISH.
topNoNumber of results (default 10, max 25).
categoryNoCategory filter (e.g., 'AI', 'Integration', 'Data and Analytics').
license_modelNoLicense model filter.

Tool Definition Quality

A4.7/5.0
Behavior4/5

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

No annotations provided, description carries the burden. It clearly explains the search behavior, filtering options, and output. However, it does not disclose any rate limits or potential side effects, but as a search tool, it is sufficiently transparent.

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?

Well-structured with bold summary, function call example, use case list, exclusions, parameter details, and output explanation. Every sentence is valuable and front-loaded.

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?

For a search tool with 4 parameters and no output schema, the description covers purpose, usage, parameters, and return format comprehensively. No gaps remain.

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%, baseline 3. Description adds value by providing examples for query, explaining default/max for top, listing categories, and enum for license_model. It also describes the output format, which is not in 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?

Description clearly states 'Search the SAP Discovery Center service catalog to find SAP BTP services', specifies verbs like 'find', 'discover', 'browse', and lists concrete use cases. It distinguishes itself from siblings like sap_discovery_center_service and search.

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?

Explicit when-to-use (e.g., 'Find which SAP BTP services are available for a specific use case') and when-not-to-use ('Do NOT use this for ABAP documentation... use the 'search' tool for those'). Also provides follow-up action: 'After finding a service, use sap_discovery_center_service to get full details.'

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