Analytics Legends — SAP Analytics Intelligence

Full concept card (Consultant tier)

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 €29.90 Consultant Pass sells. On THIS endpoint the machine-access subscription is the MCP Pass (€39.90/month, analyticslegends.ai/pricing/), which opens the ENTIRE paid tranche from one key; the €29.90 Consultant Pass is its web-subscriber equivalent and opens the same tier floor here. Requires a subscriber API key (Authorization: Bearer alk_…), Consultant tier or above; without one this tool refuses and get_concept keeps serving the public metadata. Find slugs with search_concepts.

Input Schema

TableJSON Schema

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

Output Schema

TableJSON 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.4/5.0

Behavior5/5

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

Annotations already mark readOnly/idempotent/non-destructive, and the description adds key behavioral traits: the paywall boundary, the requirement for a Bearer alk_… key at Consultant tier or above, refusal without it, and the fact that the same payload is returned structured in three languages. This goes well beyond annotation-only signal.

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

Conciseness2/5

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

The first sentence is information-dense, but the description then spends several clauses on pricing and pass-equivalence ('€29.90 Consultant Pass', '€39.90/month', 'analyticslegends.ai/pricing/', 'opens the same tier floor here') that do not help an agent invoke the tool. This could be shortened to the auth requirement and the get_concept fallback.

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?

For a single-parameter read-only tool with full schema coverage and an output schema, the description covers what the card contains, how to obtain a slug, the required authorization, and the fallback behavior. Nothing essential for selecting or calling the tool is missing.

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?

The schema already documents the single slug parameter with 100% coverage, including 'verbatim from search_concepts.rows[].slug'. The description repeats the search_concepts source but adds no new parameter-level meaning, so the baseline score of 3 is appropriate.

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 opens with 'FULL encyclopaedia card for one concept' and enumerates the payload: body, cheat sheet, glossary, pro tip, four analysis tables, and three languages. It also contrasts itself with get_concept, which continues serving public metadata, making the tool's role unambiguous.

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?

It explicitly states the subscription/auth prerequisite ('Requires a subscriber API key... Consultant tier or above'), the failure mode without it ('this tool refuses'), and the alternative ('get_concept keeps serving public metadata'). It also directs callers to find slugs with search_concepts, which is the correct retrieval path.

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 Analytics Intelligence 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.