Analytics Legends — SAP AI & Analytics MCP Server

Search the SAP AI & analytics concept encyclopaedia

search_concepts

Read-only

Search the SAP AI & analytics concept encyclopaedia (the stack's vocabulary): slug, title, category, level, editor's summary. Full card: get_concept_card (paid). Public.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_concepts"
  }
}

Input Schema

Name	Required	Description
`limit`	No
`query`	No	All words must match.
`cursor`	No
`category`	No	Category name or prefix, e.g. datasphere.

Output Schema

Name	Required	Description	Default
`rows`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed16 schema fields changedNov 10, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / category / description

Previous value: -"Concept category, matched case-insensitively as an exact value OR a prefix — so category:\"datasphere\" reaches 'Datasphere Core'. The values are long human labels, not codes. DO NOT GUESS THEM FROM THIS TEXT: the live vocabulary with a row count per label comes back as `_meta.available_categories` on EVERY call, including a call that matched nothing. A list written here would say 14 labels with 2026-07-30 counts; the corpus holds 15 today, and five of those counts have moved. Read the envelope, not the prose."New value: +"Category name or prefix, e.g. datasphere."

removedInput schema / properties / cursor / description

Removed value: -"Opaque token from a previous response's `_meta.next_cursor`. Pass it back with the SAME filter arguments; `null` means the last page. Changing a filter refuses the cursor."

removedInput schema / properties / cursor / maxLength
```
Removed value: -512
```
removedInput schema / properties / limit / description
```
Removed value: -"Max rows (hard cap 50)."
```
removedInput schema / properties / limit / maximum
```
Removed value: -50
```
removedInput schema / properties / limit / minimum
```
Removed value: -1
```

changedInput schema / properties / query / description

Previous value: -"Free-text filter, case-insensitive. EVERY word must appear in the record (substring per word, any order), so a natural-language phrase narrows the answer instead of having to match verbatim."New value: +"All words must match."

addedInput schema / properties / query / examples
```
Added value: +[
+  "data product"
+]
```
removedInput schema / properties / query / maxLength
```
Removed value: -200
```
removedOutput schema / properties / _attribution
```
Removed value: -{
-  "type": "string"
-}
```

removedOutput schema / properties / _meta

Removed value: -{
-  "type": "object"
-}

removedOutput schema / properties / result_count
```
Removed value: -{
-  "type": "integer"
-}
```

removedOutput schema / properties / rows / items

Removed value: -{
-  "properties": {
-    "citation_scope": {
-      "enum": [
-        "record",
-        "section_hub"
-      ],
-      "type": "string"
-    },
-    "citation_url": {
-      "type": "string"
-    },
-    "slug": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "title": {
-      "type": [
-        "string",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}

removedOutput schema / properties / tool

Removed value: -{
-  "type": "string"
-}

changedOutput schema / required

Previous value: -[
-  "tool",
-  "result_count",
-  "rows",
-  "_attribution"
-]New value: +[
+  "rows"
+]

Changed1 schema field changedAug 26, 2026

changedInput schema / properties / query / description

Previous value: -"Free-text filter, matched case-insensitively."New value: +"Free-text filter, case-insensitive. EVERY word must appear in the record (substring per word, any order), so a natural-language phrase narrows the answer instead of having to match verbatim."

Changed1 schema field changedAug 23, 2026

changedInput schema / properties / cursor / description

Previous value: -"Opaque token from a previous response's `_meta.next_cursor`. Pass it back with the SAME filter arguments to read the next page; a null `next_cursor` means you have reached the end. It is bound to those filters and refused if they change — a cursor names a POSITION in one ordering, and applying it to another query would start the page in the wrong place."New value: +"Opaque token from a previous response's `_meta.next_cursor`. Pass it back with the SAME filter arguments; `null` means the last page. Changing a filter refuses the cursor."

Changed1 schema field changedAug 10, 2026

changedInput schema / properties / category / description

Previous value: -"Concept category, matched case-insensitively as an exact value OR a prefix. The 14 real values are long labels, measured 2026-07-30: Generative AI Foundations (55), Joule & SAP AI (42), Career & Practice (29), Governance & Compliance (25), Architecture & Performance (25), SAC (Analytics Cloud) (22), BDC Platform (22), Adjacent Stacks (19), Datasphere Core (17), Sales & Commercial (16), Productivity & AI (10), Industry Solutions (10), BW/4HANA & Migration (9), Data Engineering & Integration (1). So category:\"datasphere\" reaches Datasphere Core."New value: +"Concept category, matched case-insensitively as an exact value OR a prefix — so category:\"datasphere\" reaches 'Datasphere Core'. The values are long human labels, not codes. DO NOT GUESS THEM FROM THIS TEXT: the live vocabulary with a row count per label comes back as `_meta.available_categories` on EVERY call, including a call that matched nothing. A list written here would say 14 labels with 2026-07-30 counts; the corpus holds 15 today, and five of those counts have moved. Read the envelope, not the prose."

Changed1 schema field changedAug 10, 2026

addedInput schema / properties / cursor

Added value: +{
+  "description": "Opaque token from a previous response's `_meta.next_cursor`. Pass it back with the SAME filter arguments to read the next page; a null `next_cursor` means you have reached the end. It is bound to those filters and refused if they change — a cursor names a POSITION in one ordering, and applying it to another query would start the page in the wrong place.",
+  "maxLength": 512,
+  "type": "string"
+}

Changed3 schema fields changedJul 31, 2026
- removedOutput schema / properties / rows / items / properties / citation_note
```
Removed value: -{
-  "type": "string"
-}
```
- changedOutput schema / properties / rows / items / properties / slug / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / rows / items / properties / title / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
Changed3 schema fields changedJul 31, 2026
- addedOutput schema / properties / rows / items / properties / citation_note
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / rows / items / properties / citation_scope
```
Added value: +{
+  "enum": [
+    "record",
+    "section_hub"
+  ],
+  "type": "string"
+}
```
- addedOutput schema / properties / rows / items / properties / citation_url
```
Added value: +{
+  "type": "string"
+}
```
First observedJul 30, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Beyond readOnlyHint/openWorldHint, the description discloses that results are shallow summary records, that expanding to a full card requires a separate paid call, and that the endpoint is public (no auth). Pagination via cursor and any result-count behaviour are left implicit, which keeps it from a 5.

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?

Front-loaded with the verb and resource, followed by return fields and the alternative route; no wasted clauses. The telegraphic fragments ('Public.') read as notes rather than prose, which slightly hurts readability but still carries real information.

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?

An output schema exists, so return structure need not be described; the definition covers scope, access, and the paid upgrade path. What is missing is pagination behaviour for cursor and the meaning/default of limit, the two undocumented parameters.

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 only 50% (limit and cursor have no descriptions), but the description compensates: the listed fields indicate what is searchable/surfaced, and the surrounding context makes the paid-vs-free distinction that shapes query strategy. Not enough for a 5 given cursor/limit semantics remain unexplained.

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?

States a specific verb and resource ('Search the SAP AI & analytics concept encyclopaedia') and scopes it as the stack's vocabulary, then names the fields returned (slug, title, category, level, editor's summary). It explicitly distinguishes itself from the sibling get_concept_card, so an agent can separate the two without opening a schema.

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?

Gives a clear routing rule: use this for lightweight discovery, use get_concept_card when the full card is needed, plus the cost signal '(paid)'. It stops short of explicit when-not-to-use conditions (e.g. when to prefer get_concept or query_knowledge_graph), so it is strong but not exhaustive.

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

All Analytics Legends — SAP AI & Analytics MCP Server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.