Analytics Legends — SAP AI & Analytics MCP Server

Local partner or acquisition candidates for a market entry (MCP Pass)

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 the API key of an MCP Pass or Firm account (the Consultant and Legend web plans do not include MCP access). No person, no e-mail — outreach details stay behind the platform's signed-URL path.

Input 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

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?

Well beyond the annotations (which already establish a safe, idempotent read), the description discloses access prerequisites ('Requires the API key of an MCP Pass or Firm account — the Consultant and Legend web plans do not include MCP access'), the return row shape, cursor pagination, and an explicit privacy boundary ('No person, no e-mail'). These are the operational facts an agent needs before calling.

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?

Material is front-loaded: population, then the local_only rationale, then filters, output, ordering, constraints, auth. Some phrasing is dense and parenthetical (e.g. 'read from the brand-family key of the SSOT'), slightly taxing on first read, but every sentence carries distinct information.

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 7-parameter, cursor-paginated read tool with an output schema and rich annotations, nothing an agent needs is missing: target-market requirement, filter semantics, ordering, pagination, auth, and what the rows contain. Sibling tools and an output schema cover the rest.

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 adds real semantics: the country/region gating that the schema does not enforce (zero required parameters), the cursor's 'same filter arguments' contract, and the ranking order by SAP signal then completeness. Some repetition of the schema's declared-module and sister-country wording keeps it from a 5.

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?

Opens with a specific verb and a precisely bounded population: '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.' The local_only contrast ('a subsidiary of a global group is a competitor, not a partner') makes it unmistakable against broader firm-search siblings such as search_firms or find_sap_clients.

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?

Explicit about the mandatory context — '`country` or `region` is required: a partner search without a target market is the whole directory' — and about the local_only toggle's intended meaning. It even routes to count_firms_by for the module vocabulary. It stops short of naming a specific sibling it should be preferred over, so it is clear context rather than full alternative routing.

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.