Skip to main content
Glama
marianfoo

SAP Documentation MCP Server

sap_discovery_center_service

Retrieve comprehensive SAP BTP service details including pricing plans, product roadmap, documentation links, and key features from the SAP Discovery Center.

Instructions

GET SAP BTP SERVICE DETAILS: sap_discovery_center_service(serviceId="abc-123-def")

FUNCTION NAME: sap_discovery_center_service

Get comprehensive details for a specific SAP BTP service from the SAP Discovery Center, including pricing plans with per-unit costs, product roadmap, documentation links, and key features.

Use this tool when you need to:

  • Get pricing information for a BTP service (plans, metrics, costs per unit, free tier availability)

  • View the product roadmap and upcoming features planned for a service

  • Find official documentation, tutorials, and community resources for a service

  • Understand service plans and their differences (free tier vs. standard vs. extended)

  • Get the SAP cost calculator link or SAP Store link for a service

  • Learn about key features and capabilities of a specific service (headlines)

  • Check what billing metrics a service uses (e.g., Capacity Units, API Calls)

You can pass either a UUID from search results OR the service name directly (e.g., "SAP Build Code", "SAP AI Core", "SAP HANA Cloud"). The tool will auto-resolve names to UUIDs.

PARAMETERS: • serviceId (required): Service UUID from search results OR the service name (e.g., "SAP Build Code"). Names are auto-resolved via search. • currency (optional, default "USD"): Pricing currency code (e.g., "EUR", "USD", "GBP"). • include_roadmap (optional, default true): Include product roadmap data with planned features by quarter. • include_pricing (optional, default true): Include pricing plans with per-unit costs and billing metrics.

RETURNS (JSON): • Core: name, description, category, productType, licenseModelType, tags, csnComponent • links: calculator, sapStore, featureDescription, discoveryCenter URLs • headlines[]: Key feature highlights with descriptions • resources: Documentation links grouped by type (documentation, tutorials, community, support, calculator) • metrics[]: Billing metric definitions (name, description, code) • pricing[]: Service plans with planName, planCode, description, usageType, features, and commercialModels (model, metric, chargingPeriod, pricePerUnit, blockSize). The pricing section contains actual per-unit prices from the SAP Discovery Center (e.g., "1.04 EUR" per Capacity Unit/month). • roadmap: Planned features organized by quarter with categories and deliverables (or null if no roadmap exists)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
serviceIdYesService UUID from search results OR service name (e.g., 'SAP Build Code'). Names are auto-resolved.
currencyNoPricing currency code (default 'USD').
include_roadmapNoInclude product roadmap (default true).
include_pricingNoInclude pricing plans (default true).
Behavior4/5

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

No annotations provided; description carries full burden. It discloses auto-resolution of serviceId, default parameter values, and detailed return structure. Does not mention error handling or rate limits, but overall transparent for a read operation.

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?

Description is front-loaded with a concise function signature, then organized into use-case bullets and detailed sections. Slightly verbose in the return structure but well-structured and informative.

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, the description provides a comprehensive return structure (JSON fields). Covers use cases, parameter details, auto-resolution, and defaults. Complete for a moderately complex tool.

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%, and description adds valuable semantics: auto-resolution for serviceId, default currency 'USD', and defaults for boolean flags. All parameters are explained beyond 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?

The description explicitly states 'GET SAP BTP SERVICE DETAILS' and lists specific data returned (pricing, roadmap, documentation). This clearly distinguishes it from sibling tools like sap_discovery_center_search (search) and sap_get_object_details (general details).

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 description provides a bulleted list of when to use, covering pricing, roadmap, docs, service plans, etc. It does not explicitly state when not to use, but it implies context (e.g., needing a service name or UUID). Lacks explicit alternatives but clear context.

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