Analytics Legends — SAP Analytics Intelligence

Traverse the learning knowledge graph

query_knowledge_graph

Read-onlyIdempotent

The RELATIONS between the platform's teaching objects — which Academy module teaches which concept, which study covers which module, what a concept relates to. THIS IS THE ONLY TOOL ON THIS SERVER THAT SERVES EDGES; the others serve rows. Ask it what connects to what, not what exists. SCOPE, AND IT IS NARROWER THAN 'the knowledge graph': it carries four node types — concept, module, study, vendor — and every edge whose BOTH endpoints are one of them. The whole graph holds eleven node types; the seven it does not carry are each either served by their own tool or named as not served at all, and _meta.excluded_node_types says which per type (consultant data is served at NO tier), so a missing type is a documented boundary and never a silent gap. Call it with node_id (e.g. module:M178, concept:C001, study:ai-impact-2026-EN) to walk one node's neighbourhood; with node_type and/or query to find a node id first. edge_type and direction narrow a walk. Read _meta.available_edge_types — computed from the served projection on every call — before assuming an edge type exists.

Input Schema

TableJSON Schema

Name	Required	Description
`lang`	No	ISO-639-1 language for the LABELS — en, fr or de. Defaults to en. The fallback is declared and never silent: the language asked for, then English, then French, and `_meta.label_language_coverage` says on how many nodes each language is actually filled. Concept and module titles carry French; German arrives as the corpus is translated, and an untranslated node falls back rather than being hidden.
`limit`	No	Max rows (hard cap 50).
`query`	No	Case-insensitive substring of a node's label. Applies to the NODE listing, not to a walk. Matched against the label SERVED, so it follows `lang`.
`cursor`	No	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.
`node_id`	No	Fully-qualified node id, `<type>:<id>` — `module:M178`, `concept:C001`, `study:ai-impact-2026-EN`, `vendor:alteryx`. With it, rows are that node's EDGES (one row per neighbour). Without it, rows are NODES.
`direction`	No	Which side of the edge `node_id` must sit on. Default `both`. Ignored without `node_id`, and the response says so rather than pretending it applied.
`edge_type`	No	Restrict a walk to one relation. The served projection carries FIVE — teaches · taught_by · covers · related · mentions — and this list is a HINT, not the authority: read `_meta.available_edge_types`, computed on every call. A four-name list stood here while the projection served five, so `mentions` was reachable and undocumented.
`node_type`	No	Restrict to one carried node type: concept · module · study · vendor. Read `_meta.available_node_types`.

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. Dates show when Glama detected each change.

Changed4 schema fields changedSep 3, 2026

addedInput schema / properties / lang

Added value: +{
+  "description": "ISO-639-1 language for the LABELS — en, fr or de. Defaults to en. The fallback is declared and never silent: the language asked for, then English, then French, and `_meta.label_language_coverage` says on how many nodes each language is actually filled. Concept and module titles carry French; German arrives as the corpus is translated, and an untranslated node falls back rather than being hidden.",
+  "pattern": "^[A-Za-z]{2}$",
+  "type": "string"
+}

changedInput schema / properties / query / description

Previous value: -"Case-insensitive substring of a node's label. Applies to the NODE listing, not to a walk."New value: +"Case-insensitive substring of a node's label. Applies to the NODE listing, not to a walk. Matched against the label SERVED, so it follows `lang`."

addedOutput schema / properties / rows / items / properties / label / description

Added value: +"In the language asked for when the node carries it, else the declared fallback — see `label_lang`."

addedOutput schema / properties / rows / items / properties / label_lang

Added value: +{
+  "description": "The language the served `label` is actually written in. It differs from the requested `lang` exactly when that translation does not exist.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

Changed1 schema field changedAug 27, 2026

changedInput schema / properties / edge_type / description

Previous value: -"Restrict a walk to one relation (teaches · taught_by · covers · related). Read `_meta.available_edge_types` — it is computed, never written here."New value: +"Restrict a walk to one relation. The served projection carries FIVE — teaches · taught_by · covers · related · mentions — and this list is a HINT, not the authority: read `_meta.available_edge_types`, computed on every call. A four-name list stood here while the projection served five, so `mentions` was reachable and undocumented."

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."

AddedAug 14, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already provide readOnly=true, idempotent=true, destructive=false, and openWorld=false, and the description adds substantial behavior beyond them: the closed-world boundary is explicit ('a missing type is a documented boundary and never a silent gap'), the edge_type list is disclosed as 'a HINT, not the authority' with a historical failure incident (mentions reachable but undocumented), lang fallback is declared non-silent with coverage metadata, and changing a filter 'refuses the cursor'. No contradiction with the annotations.

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?

Long but dense — every sentence earns its place (purpose, differentiation, scope boundary, call modes, meta-guidance) and the key differentiators are front-loaded. Minor deductions: the 'HINT, not the authority' point and the four node types are repeated in parameter schema descriptions, and the ALL-CAPS emphasis is heavy-handed.

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 tool with 8 parameters, three call modes, pagination, language fallback, and a documented scope boundary, nothing needed to invoke it correctly is missing: boundaries, modes, meta-keys (_meta.available_edge_types, _meta.excluded_node_types, _meta.label_language_coverage, _meta.next_cursor), and fallback behavior are all disclosed. An output schema exists, so return-value structure need not be in the description.

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?

Schema description coverage is 100% and the parameter descriptions are themselves rich, so the baseline is 3. The tool description adds genuine cross-parameter meaning: the walk-vs-find mode distinction (node_id present => edges, absent => nodes), the sequencing guidance to 'find a node id first' with node_type/query, and the rule that edge_type/direction merely narrow a walk. That pushes it above baseline, though part of the mode distinction is also stated in the node_id schema description.

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 states a precise verb+resource — query/traverse the SERVED EDGES of the knowledge graph — and immediately differentiates it from every sibling: 'THIS IS THE ONLY TOOL ON THIS SERVER THAT SERVES EDGES; the others serve rows. Ask it what connects to what, not what exists.' It enumerates the four carried node types and gives concrete relation examples, so an agent cannot confuse it with get_concept, get_study, or the search tools.

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?

Explicit when-to-use guidance is present and contrasts directly with alternatives: use it for relations, not existence ('the others serve rows'), and the seven excluded node types are 'each either served by their own tool or named as not served at all'. It also separates the two call modes — walk with node_id vs. find with node_type/query — and names the hard boundary case (consultant data is served at NO tier).

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0

Disambiguation4/5

Each tool targets a distinct resource or action (firms, clients, modules, concepts, studies, opportunities, rates, news, knowledge graph). Some pairs like find_academy_modules vs list_sap_modules and find_sap_clients vs search_firms could be confused, but the descriptions explicitly disambiguate them.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in lowercase snake_case: find_, get_, list_, search_, count_, query_. Verbs are consistently used for their roles (find/search for querying, get for single items, list for enumerations), with no mixed casing or style.

Tool Count4/5

20 tools is on the higher end, but the server covers a broad domain with multiple distinct datasets (directory, clients, academy, concepts, studies, opportunities, rates, news, graph). Each tool earns its place, though the count is slightly above the ideal 3-15 range.

Completeness5/5

The domain is a read-only intelligence platform, and it provides search/list and get operations for every major entity: firms, clients, modules, concepts, studies, and opportunities. The knowledge graph adds relational querying, and rates/news are covered. No essential lifecycle operations are missing for the stated purpose.

Traverse the learning knowledge graph

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources