Skip to main content
Glama
marianfoo

SAP Note Search MCP Server

by marianfoo
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Server Quality Checklist

67%
Profile completionA complete profile improves this server's visibility in search results.

  • Latest release: v1.0.0

  • Disambiguation5/5

    The two tools have perfectly distinct purposes: sap_note_search is for finding relevant SAP Notes based on a query, while sap_note_get is for retrieving detailed content for a specific note ID. Their descriptions clearly differentiate them, with no overlap in functionality, making it impossible for an agent to confuse them.

    Naming Consistency5/5

    Both tools follow a consistent snake_case naming pattern with the prefix 'sap_note_' followed by a verb (search, get). This uniformity makes the tool set predictable and easy to understand, adhering to a clear convention throughout.

    Tool Count3/5

    With only two tools, the server feels thin for its domain of SAP Note search and retrieval. While the tools cover the core workflow (search and get), the low count might limit functionality, such as lacking tools for filtering, sorting, or managing notes, which could be expected in a more comprehensive SAP support system.

    Completeness4/5

    The tool set effectively covers the essential workflow for accessing SAP Notes: searching for notes and retrieving detailed content. However, there are minor gaps, such as no tools for updating, deleting, or listing all notes, which might be less critical here but could enhance completeness for broader note management scenarios.

  • Average 4.8/5 across 2 of 2 tools scored.

    See the Tool Scores section below for per-tool breakdowns.

  • This repository is archived. Archived repositories automatically receive an F maintenance tier.

  • This repository is licensed under Apache 2.0.

  • This repository includes a README.md file.

  • No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.

    Tip: use the "Try in Browser" feature on the server page to seed initial usage.

  • Add a glama.json file to provide metadata about your server.

  • If you are the author, simply .

    If the server belongs to an organization, first add glama.json to the root of your repository:

    {
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}

    Then . Browse examples.

  • Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

  • Behavior5/5

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

    With no annotations provided, the description carries the full burden of behavioral disclosure. It thoroughly describes behavioral traits: it explains the tool's role in a workflow (search → get pattern), provides error handling details (e.g., common errors like 'Note not found' or 'Access denied' with solutions), and includes best practices (e.g., limit fetches to 2-3 notes, validate ID format). This goes beyond basic functionality to cover operational context and constraints.

    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 (e.g., USE WHEN, DO NOT USE WHEN, PARAMETER REQUIREMENTS), making it easy to navigate. However, it is lengthy due to extensive details like error handling and best practices. While every section adds value, it could be more concise by integrating some points (e.g., merging parameter examples with schema info). Overall, it's front-loaded with key purpose but includes necessary elaboration.

    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 complexity (fetching detailed SAP Notes) and the presence of an output schema (which handles return values), the description is highly complete. It covers purpose, usage guidelines, parameter semantics, workflow patterns, error handling, and best practices. With no annotations, it compensates by providing all necessary context for the agent to use the tool effectively, including sibling tool relationships and operational constraints.

    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?

    The schema description coverage is 100%, so the baseline is 3. The description adds significant value beyond the schema: it provides a 'PARAMETER REQUIREMENTS' section with detailed examples of valid and invalid Note IDs, instructions for extracting IDs from user input, and practical guidance on usage. While the schema covers the technical details, the description enhances understanding with real-world context and preprocessing steps.

    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 the tool's purpose: 'Fetch complete content and metadata for a specific SAP Note by ID.' It specifies the verb ('fetch'), resource ('SAP Note'), and distinguishes from its sibling sap_note_search by emphasizing detailed content retrieval versus searching. The description explicitly lists what the note contains, reinforcing the comprehensive nature of the fetch.

    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 guidance with dedicated 'USE WHEN' and 'DO NOT USE WHEN' sections. It clearly states when to use this tool (e.g., after search results, for detailed content) and when not to (e.g., without a Note ID, for browsing). It explicitly names the alternative tool (sap_note_search) and outlines a workflow pattern, ensuring the agent understands the context and prerequisites.

    Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

  • Behavior5/5

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

    Since no annotations are provided, the description carries the full burden of behavioral disclosure. It thoroughly explains important behavioral aspects: S-user credentials required for full content access, note ID format, ranking methodology, language defaults, and workflow patterns with sibling tools. This provides comprehensive behavioral context beyond basic functionality.

    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 and headings, making it easy to navigate. While comprehensive, it maintains focus on relevant information without unnecessary fluff. Some sections could be slightly more concise, but overall the structure enhances readability and information retrieval.

    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 complexity (search functionality with specific domain knowledge requirements), no annotations, rich input schema, and presence of an output schema, the description provides excellent completeness. It covers purpose, usage guidelines, behavioral aspects, parameter guidance, workflow patterns, and important notes, making it highly comprehensive for agent understanding.

    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?

    With 100% schema description coverage, the baseline is 3. The description adds significant value by providing extensive query construction guidance, examples of effective vs. ineffective queries, and specific query formulas. While the schema already documents parameters well, the description's additional context about query strategy and examples enhances understanding.

    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 the tool searches the SAP Knowledge Base for specific types of content (troubleshooting articles, bug fixes, patches, etc.) and returns ranked results with metadata. It explicitly distinguishes this from sibling tools by explaining what SAP Notes are and what they contain, making the purpose specific and well-defined.

    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 'USE WHEN' and 'DO NOT USE WHEN' sections with detailed scenarios and named alternatives (sap_help_search, sap_community_search). It gives clear guidance on when to use this tool versus others, including specific user queries and contexts.

    Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

GitHub Badge

Glama performs regular codebase and documentation scans to:

  • Confirm that the MCP server is working as expected.
  • Confirm that there are no obvious security issues.
  • Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

mcp-sap-notes MCP server

Copy to your README.md:

Score Badge

mcp-sap-notes MCP server

Copy to your README.md:

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-notes'

If you have feedback or need assistance with the MCP directory API, please join our Discord server