Analytics Legends — SAP AI & Analytics MCP Server

Full concept card (MCP Pass)

get_concept_card

Read-onlyIdempotent

The FULL encyclopaedia card for one concept — body, cheat sheet, glossary, pro tip, and the four analysis tables (decision table, peer comparison, named pitfalls, performance facts), EN, FR and DE, plus why-it-matters and key points (those two are also published free on the concept page; here they come structured, in three languages, in the same payload) — the corpus the Consultant web plan sells. On THIS endpoint the paid tranche is opened by the MCP Pass (€29.90/month, analyticslegends.ai/mcp-server/) or the Firm Pass, from one key; the Consultant and Legend web plans do not include MCP access. Requires the API key of an MCP Pass or Firm account (Authorization: Bearer alk_…) — the Consultant and Legend web plans do not include MCP access; without one this tool refuses and get_concept keeps serving the public metadata. Find slugs with search_concepts.

Input Schema

Name	Required	Description	Default
`slug`	Yes	Concept slug, verbatim from search_concepts.rows[].slug.

Output Schema

Name	Required	Description	Default
`rows`	Yes
`tool`	Yes
`_meta`	No
`_attribution`	Yes
`result_count`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedJul 31, 2026
- changedOutput schema / properties / rows / items / properties / body_en / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- 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_en / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
AddedJul 31, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Adds substantial behavior beyond the read-only, idempotent annotations: paid access gating, required Bearer key, refusal behavior, and the exact premium content returned in EN/FR/DE. The annotations already cover safety, and the description adds the access and content context an agent needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The important content is front-loaded, but the description is a long run-on sentence followed by repeated access-plan wording. The Consultant/Legend exclusion is stated twice, and the pricing URL plus lengthy contents list make it more verbose than necessary.

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 output schema exists, the description does not need to explain return values and instead covers the critical access, content, and alternative-tool context. An agent has enough information to decide whether to call it and what prerequisites apply.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single slug parameter is already documented as coming verbatim from search_concepts.rows[].slug. The description only repeats the search_concepts pointer, so it adds little semantic value 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?

States a specific verb and resource: retrieves the FULL encyclopaedia card for one concept, and enumerates the included sections and languages. It clearly distinguishes this from get_concept by noting that get_concept serves public metadata while this tool opens the paid tranche.

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?

Explicitly explains when this tool is usable: only with an MCP Pass or Firm Pass API key, and it refuses without one. It names alternatives and prerequisites: use search_concepts to find slugs, and get_concept continues serving public metadata when access is missing.

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.