Analytics Legends — SAP AI & Analytics MCP Server

Get one firm's published profile

get_firm

Read-onlyIdempotent

Fetch one organisation from the published directory by its database slug (rows[].slug from search_firms, verbatim). Returns the same public fields plus partnerships_declared, the count of partnerships this directory records for the firm — 0 on ~77 % of rows (re-measured 2026-09-30 on the published tranche: 77,1 %; it read ~97 % until the 2026-09-30 brand-family pass derived 3 730 sibling links from sister entities), meaning none recorded here, never that the firm has no partners; a sibling link is a reading of shared brand, not a declared org chart. Does not return the paid firm-intelligence profile, contacts, or any person.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes	The DATABASE slug, taken verbatim from search_firms.rows[].slug. It is not always the web slug in citation_url: a minority of published rows carry a numeric firm id instead (365 of them on 2026-08-09 — the population is read at query time and returned as `_meta.tranche_total_row_count`, never written down here). get_firm{slug:"00393"} is GULP, whose page is /companies/gulp/. Deriving a slug from the citation URL fails on those rows, and deriving it from the NAME is not safe either; carry rows[].slug across instead. A slug this tool refuses is not proof the firm is absent from the market or even from the database — the published tranche is an editorial subset, and a row the editor has not published is refused here exactly as a wrong slug is.

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.

Changed1 schema field changedAug 9, 2026

changedInput schema / properties / slug / description

Previous value: -"The DATABASE slug, taken verbatim from search_firms.rows[].slug. It is not always the web slug in citation_url: re-measured 2026-07-31 against the tranche this tool actually serves (5 157 published rows), 429 of them (8,3 %) carry a numeric firm id instead — '00317' is BearingPoint Switzerland, whose page is /companies/bearingpoint-switzerland/. Deriving a slug from the citation URL fails on those rows; carry rows[].slug across instead."New value: +"The DATABASE slug, taken verbatim from search_firms.rows[].slug. It is not always the web slug in citation_url: a minority of published rows carry a numeric firm id instead (365 of them on 2026-08-09 — the population is read at query time and returned as `_meta.tranche_total_row_count`, never written down here). get_firm{slug:\"00393\"} is GULP, whose page is /companies/gulp/. Deriving a slug from the citation URL fails on those rows, and deriving it from the NAME is not safe either; carry rows[].slug across instead. A slug this tool refuses is not proof the firm is absent from the market or even from the database — the published tranche is an editorial subset, and a row the editor has not published is refused here exactly as a wrong slug is."

Changed3 schema fields changedJul 31, 2026
- removedOutput schema / properties / rows / items / properties / citation_note
```
Removed value: -{
-  "type": "string"
-}
```
- changedOutput schema / properties / rows / items / properties / name / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / rows / items / properties / slug / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```

Changed4 schema fields changedJul 31, 2026

changedInput schema / properties / slug / description

Previous value: -"The DATABASE slug, taken verbatim from search_firms.rows[].slug. It is not always the web slug in citation_url: re-measured 2026-07-30 against the tranche this tool actually serves, 485 of the 6 437 rows (7,5 %) carry a numeric firm id instead — '00317' is BearingPoint Switzerland, whose page is /companies/bearingpoint-switzerland/. Deriving a slug from the citation URL fails on those rows; carry rows[].slug across instead."New value: +"The DATABASE slug, taken verbatim from search_firms.rows[].slug. It is not always the web slug in citation_url: re-measured 2026-07-31 against the tranche this tool actually serves (5 157 published rows), 429 of them (8,3 %) carry a numeric firm id instead — '00317' is BearingPoint Switzerland, whose page is /companies/bearingpoint-switzerland/. Deriving a slug from the citation URL fails on those rows; carry rows[].slug across instead."

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"
+}
```

Changed1 schema field changedJul 30, 2026

changedInput schema / properties / slug / description

Previous value: -"The DATABASE slug, taken verbatim from search_firms.rows[].slug. It is not always the web slug in citation_url: measured 2026-07-30, 516 of the 6 496 rows (7,9 %) carry a numeric firm id instead — '00317' is BearingPoint Switzerland, whose page is /companies/bearingpoint-switzerland/. Deriving a slug from the citation URL fails on those rows; carry rows[].slug across instead."New value: +"The DATABASE slug, taken verbatim from search_firms.rows[].slug. It is not always the web slug in citation_url: re-measured 2026-07-30 against the tranche this tool actually serves, 485 of the 6 437 rows (7,5 %) carry a numeric firm id instead — '00317' is BearingPoint Switzerland, whose page is /companies/bearingpoint-switzerland/. Deriving a slug from the citation URL fails on those rows; carry rows[].slug across instead."

Changed1 schema field changedJul 30, 2026

changedInput schema / properties / slug / description

Previous value: -"Firm slug, e.g. 'accenture'. From search_firms.rows[].slug."New value: +"The DATABASE slug, taken verbatim from search_firms.rows[].slug. It is not always the web slug in citation_url: measured 2026-07-30, 516 of the 6 496 rows (7,9 %) carry a numeric firm id instead — '00317' is BearingPoint Switzerland, whose page is /companies/bearingpoint-switzerland/. Deriving a slug from the citation URL fails on those rows; carry rows[].slug across instead."

First observedJul 30, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, non-destructive, closed-world), and the description goes well beyond them by explaining what partnerships_declared actually means, warning that 0 indicates 'none recorded here' rather than 'no partners', and clarifying that a sibling link is an inference of shared brand, not a declared org chart. That interpretation guidance is exactly the kind of context annotations cannot supply.

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?

Front-loaded correctly — action first, then return-shape caveats — but it is over-stuffed with measurement trivia: precise percentages with comma decimals, multiple re-measurement dates, and the historical '~97 % until the brand-family pass' narrative. The core warning about misreading 0 earns its place; the surrounding statistics are heavier than an agent needs.

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?

Single required parameter, output schema present, annotations covering read-only/idempotent/closed-world, and the description still adds the interpretation caveats an agent needs to avoid false conclusions (empty partnerships, slug refusal not implying absence). Nothing required to call it correctly 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?

Schema description coverage is 100% and the slug property description is itself extremely detailed, so the schema does the heavy lifting. The description reinforces the 'verbatim from search_firms.rows[].slug' rule but adds little semantic detail beyond what the schema already states; baseline 3 applies.

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 ('Fetch one organisation from the published directory') scoped by an exact identifier source, and distinguishes itself from siblings by explicitly excluding the paid firm-intelligence profile (get_firm_intel) and search_firms' list output. An agent can route correctly without opening any 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 concrete context for use: pull rows[].slug from search_firms verbatim to call this. The exclusion of the paid firm-intelligence profile implicitly points to get_firm_intel, but the description never names that alternative or states the condition under which to prefer it, so the when-not side is implied rather than explicit.

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.

Get one firm's published profile

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources