Skip to main content
Glama
marianfoo

SAP Documentation MCP Server

by marianfoo
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

sap_community_search

Search SAP Community blogs, Q&A, and discussions for practical troubleshooting and real-world experiences. Retrieve full content of top matching posts.

Instructions

SEARCH SAP COMMUNITY: sap_community_search(query="search terms")

FUNCTION NAME: sap_community_search

Dedicated search across SAP Community blogs, Q&A posts, and discussions. Returns full content of the top matching posts.

IMPORTANT: The main search tool (with includeOnline=true) already includes SAP Community results alongside offline docs, SAP Help, and Software Heroes. Use this dedicated tool only when: • The main search tool returned no useful results for your question • You are looking for specific error messages, runtime exceptions, or obscure symptoms • You need practical workarounds, troubleshooting steps, or real-world implementation experiences not covered in official documentation • You want to see full community post content (not just snippets)

This tool searches SAP Community via the Khoros LiQL API and automatically retrieves full content for the top 3 posts.

PARAMETERS: • query (required): Search terms. Use specific error messages, symptoms, or technical terms for best results. • k (optional, default=30): Number of results to return. • minKudos (optional, default=1): Minimum number of kudos (likes) a post must have.

  • Default 1 filters out zero-engagement posts, giving higher-quality results.

  • Set to 0 for the broadest possible search (includes all posts, even those with no engagement — useful when looking for very niche or recent topics).

  • Set higher (e.g. 5 or 10) to surface only well-received, community-validated content.

  • Suggested maximum: 10. Higher values may return very few or no results.

RETURNS (JSON with): • results: Array of community posts, each containing:

  • id: Post identifier (use with fetch to retrieve full content later)

  • title: Post title

  • url: Direct link to the SAP Community post

  • snippet: Text excerpt

  • metadata.author: Post author

  • metadata.likes: Number of kudos

  • metadata.tags: Topic tags

WORKFLOW:

  1. Start with search(query="your question") (includes community + other sources)

  2. If results are insufficient, use sap_community_search(query="specific error or symptom")

  3. Use fetch(id="community-...") to retrieve full content of any community post from either tool

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch terms for SAP Community, in ENGLISH (corpus is primarily English). Be specific - use error messages, symptoms, or technical terms.
kNoNumber of results to return. Default: 30.
minKudosNoMinimum kudos (likes) a post must have. Default 1 (filters zero-engagement posts). Set 0 for broadest search (niche/recent topics). Set higher (5-10) for well-received, community-validated content only.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultsYes

Tool Definition Quality

A4.9/5.0
Behavior5/5

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

No annotations provided, but the description fully compensates by disclosing the underlying API (Khoros LiQL), automatic full content retrieval for top 3 posts, and detailed parameter behavior (minKudos defaults and effects). It covers all relevant behavioral aspects for a search tool.

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?

The description is well-structured with clear headings (IMPORTANT, PARAMETERS, RETURNS, WORKFLOW) and front-loaded with the core purpose. Every sentence adds value, and there is no redundancy. It is concise yet comprehensive.

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?

The description is very complete, including return format details and workflow. However, there is slight ambiguity: the description says it returns results from top 3 posts but also has a k parameter for number of results. Clarifying the relationship between k and the top 3 limit would improve completeness. Still, it is fully functional.

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 the description adds significant value by explaining the semantic meaning of minKudos values, recommending specific query types like error messages, and clarifying defaults. This goes well 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 clearly states it searches SAP Community blogs, Q&A, and discussions, returning full content of top matching posts. It distinguishes from the sibling tool 'search' which already includes community results, making the purpose specific and differentiated.

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?

The description provides explicit when-to-use guidance: use the main search first, then this tool if results are insufficient or for specific scenarios like error messages. It also gives a clear workflow with steps, and explains alternatives.

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