Analytics Legends — SAP AI & Analytics MCP Server

Firm intelligence profile (MCP Pass)

get_firm_intel

Read-onlyIdempotent

The paid intelligence profile of a services firm — SAP practice size and partner level, delivery flags per product, typical day rate and seniority, notable clients, analytics practice summary, and a LinkedIn company URL (present on ~71% of the corpus, re-measured 2026-09-05 on 9,104 profiles — it read ~39% from 2026-08-10 to 2026-09-05, i.e. a third of the corpus below the truth, because an enrichment pass filled the column and no reader of this sentence was told — glassdoor_rating, glassdoor_reviews_count and linkedin_followers are null on all but a handful of profiles, absence here is a data gap, not a signal). READ THE SPARSITY BEFORE QUOTING A ROW: on the 9,103 profiles measured 2026-08-23, typical_day_rate_eur is null on 78.0% and sap_partner_level on 85.7% — the two headline fields are the exception, not the rule, and a null means 'not researched', never 'no partner level'. Requires the API key of an MCP Pass or Firm account (the Consultant and Legend web plans do not include MCP access). Person-shaped fields (contacts, founders, leadership, recruiters, postal addresses) are NEVER served by this endpoint at any tier — they remain behind the platform's signed-URL path. Search by name; the public directory (search_firms) is a different, wider population.

Input Schema

Name	Required	Description
`mode`	No	Keep only firms whose profile declares this engagement mode (mode_freelance / mode_permanent / mode_subcontract). Same reading as `delivers`: declared-only.
`name`	No	Firm name, matched case-insensitively; an exact name ranks first, then a name starting with it, then the other matches. Omit to browse the corpus by data completeness.
`limit`	No	Max rows (hard cap 10 — these rows are wide).
`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.
`country`	No	ISO-3166-1 alpha-2 country code, e.g. DE, FR, CH.
`delivers`	No	Keep only firms whose profile DECLARES delivery of this product (the `delivers_*` flags every row already carries). An undeclared flag drops the row: absence from the result means the profile does not declare it, not that the firm cannot deliver it.

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.

Changed1 schema field changedOct 2, 2026

changedInput schema / properties / name / description

Previous value: -"Firm name, matched case-insensitively. Omit to browse the corpus by data completeness."New value: +"Firm name, matched case-insensitively; an exact name ranks first, then a name starting with it, then the other matches. Omit to browse the corpus by data completeness."

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

Changed2 schema fields changedAug 17, 2026

addedInput schema / properties / delivers

Added value: +{
+  "description": "Keep only firms whose profile DECLARES delivery of this product (the `delivers_*` flags every row already carries). An undeclared flag drops the row: absence from the result means the profile does not declare it, not that the firm cannot deliver it.",
+  "enum": [
+    "datasphere",
+    "bdc",
+    "sac",
+    "bw",
+    "bw4hana",
+    "s4hana",
+    "ecc",
+    "hana",
+    "joule",
+    "businessobjects",
+    "bpc",
+    "successfactors",
+    "ariba",
+    "concur"
+  ],
+  "type": "string"
+}

addedInput schema / properties / mode

Added value: +{
+  "description": "Keep only firms whose profile declares this engagement mode (mode_freelance / mode_permanent / mode_subcontract). Same reading as `delivers`: declared-only.",
+  "enum": [
+    "freelance",
+    "permanent",
+    "subcontract"
+  ],
+  "type": "string"
+}

Changed1 schema field changedAug 9, 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 / name / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / rows / items / properties / sap_partner_level / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
AddedJul 31, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Beyond the readOnly/idempotent annotations, the description discloses things an agent cannot get elsewhere: the paid-account gate (Consultant and Legend web plans are excluded), the hard exclusion of all person-shaped fields at every tier, the LinkedIn URL coverage figure, and the critical null-vs-false distinction for typical_day_rate_eur and sap_partner_level. The weak spot is the embedded editorial aside about a past measurement error, which reads as a correction to a human reader rather than information the calling agent can act on.

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 core content is a single run-on paragraph whose most actionable warnings (null rates on headline fields, auth tier, person-field exclusion) are buried inside em-dash interjections and a lengthy parenthetical about re-measured LinkedIn coverage. The aside explaining that a prior figure was "a third of the corpus below the truth" and that "no reader of this sentence was told" is self-referential noise for an agent and pushes the operational guidance to the middle of the text.

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-format detail is not required, and the description covers the remaining agent-critical facts: auth requirements, the destructive-to-assume null semantics, the person-data exclusion, and the sibling boundary against search_firms. What keeps it short of complete is the absence of any distinction from get_firm despite near-identical naming, and the lack of a stated default behavior when name is omitted.

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 enum/filter semantics (declared-only reading of `delivers` and `mode`, cursor reuse rules, the cap of 10) are all documented in the schema itself. The description adds only the phrase "Search by name" and a general sparsity warning; it contributes essentially nothing about `country`, `limit`, or `mode` that the schema does not already say. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence names the resource concretely (a paid intelligence profile of a services firm) and enumerates the fields it carries, so an agent knows it returns a wide firm record rather than a list of names. It explicitly distinguishes itself from search_firms (public directory, wider population). It does not, however, distinguish itself from sibling get_firm or get_sap_client_profile, which leaves a real ambiguity unresolved.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Search by name" plus the tier/auth constraint implies the usage context, and the search_firms exclusion is genuinely useful routing. Missing is any statement of when an agent should prefer this over get_firm, get_sap_client_profile, or find_sap_clients, and no guidance on using the filter-only path (omitting name to browse by completeness). Usage is implied rather than prescribed.

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.