Analytics Legends — SAP AI & Analytics MCP Server

Local partner or acquisition candidates for a market entry (Legend tier)

find_partner_candidates

Read-onlyIdempotent

Rank the LOCAL service providers of a target country or region — the firms a practice partners with, subcontracts to, or acquires to enter a market. local_only (default true) keeps firms with NO sister entity in another country (read from the brand-family key of the SSOT): a subsidiary of a global group is a competitor, not a partner. Filter by kind and by DECLARED SAP module; rows carry the declared modules, the sister countries of the brand (when any), the count of declared partnerships and the public directory fields. Ordered by SAP signal, then data completeness. country or region is required: a partner search without a target market is the whole directory. Paginated by cursor. Requires a subscriber API key, Legend tier or above. No person, no e-mail — outreach details stay behind the platform's signed-URL path.

Input Schema

TableJSON Schema

Name	Required	Description
`kind`	No	Restrict to one provider kind (placement agencies, ESN/SI practices, Big-4, SAP partners, platforms). SAP's own entities, communities, schools and public bodies are never in this population.
`limit`	No	Max rows (hard cap 50).
`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.
`module`	No	Restrict to firms with a DECLARED link to one SAP module code (UPPERCASE snake_case, e.g. DATASPHERE, BDC, SAC — call count_firms_by {by:"module"} for the live vocabulary). Absence means no declared link, never incapacity.
`region`	No	Region code of the HQ country — the platform's six-value geography: EMEA (Europe AND the Middle East), AMER (North America), LATAM, APAC, AFRICA (its own region, not folded into EMEA), GLOBAL (country unknown). Case-insensitive on input; anything else is refused.
`country`	No	ISO-3166-1 alpha-2 country code, e.g. DE, FR, CH.
`local_only`	No	true (default): only firms with no sister entity abroad. false: every provider of the market, groups included.

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.

Changed2 schema fields changedOct 2, 2026

changedInput schema / properties / kind / description

Previous value: -"Restrict to one provider kind (placement agencies, ESN/SI practices, Big-4, SAP partners, platforms). Communities, schools and public bodies are never in this population."New value: +"Restrict to one provider kind (placement agencies, ESN/SI practices, Big-4, SAP partners, platforms). SAP's own entities, communities, schools and public bodies are never in this population."

changedInput schema / properties / kind / enum

Previous value: -[
-  "agency_placement",
-  "professional_services_esn",
-  "professional_services_big4",
-  "vendor_partner",
-  "vendor_sap",
-  "platform_marketplace",
-  "other"
-]New value: +[
+  "agency_placement",
+  "professional_services_esn",
+  "professional_services_big4",
+  "vendor_partner",
+  "platform_marketplace",
+  "other"
+]

AddedSep 30, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare the safe read-only/idempotent profile, but the description adds real operational context: subscriber API key with Legend-tier prerequisite, cursor pagination semantics, the ordering rule (SAP signal then data completeness), the row contents, and the privacy constraint that no person or e-mail is returned. This is information an agent cannot recover from 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?

Purpose and the key scoping constraint (local_only) are front-loaded, and every clause carries information. It is a dense single block and repeats some schema content (e.g. the local_only default), which keeps it from a 5 but is justified by the tool's complexity.

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?

Despite an output schema existing, the description still covers row shape, ordering, auth prerequisites, and pagination, and it flags the mandatory target market and the competitor-vs-partner distinction. An agent has everything needed to invoke it correctly without opening the schema.

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 coverage is 100%, so the baseline is 3, but the description goes beyond the field definitions by explaining the intent behind local_only (read from the brand-family key of the SSOT) and clarifying that a missing module link means no declared link rather than incapacity. It adds rationale and ranking semantics rather than merely restating 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?

Specific verb ('Rank') plus a precisely scoped resource ('LOCAL service providers of a target country or region' for partnering, subcontracting, or acquisition). It is clearly distinguishable from sibling searches like search_firms or find_sap_clients because it names the market-entry/partner-selection population and even excludes competitors via local_only.

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 strong contextual guidance: the local_only rationale (a global subsidiary is a competitor, not a partner), the requirement of country or region ('a partner search without a target market is the whole directory'), and points to count_firms_by for the live module vocabulary. It never explicitly states when to prefer a sibling over this tool, so it stops short of a 5.

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.