Admin Multilingual
F-007 multilingual-discovery telemetry: does the fleet, working in a non-English language, actually reach + call tools after the multilingual keyword rollout?
Signal: the DETECTED LANGUAGE of each cloud tool call's text arguments (logged as an ISO code on cloud_data_tool_called — never the text itself). A call whose args are in Spanish reaching search_emails is direct evidence that discovery worked in Spanish. Honest limits: the tool SEARCH itself is client-side and invisible; only cloud calls with detectable text args are counted (no-arg/proper-noun calls → lang null); local-socket calls aren't tagged yet.
KPI multilingual_reach = share of language-detected calls that are NON-English — the fraction of measurable usage coming from other languages. The per-language table shows how many distinct domains each language reaches (breadth = the product is usable in that language).
Request
- Base URL: https://api.local-mcp.com (the document declares no server; this is the origin it was published from)
- URL: https://api.local-mcp.com/admin/multilingual
- Auth: none declared. Required headers: x-admin-key
Query parameters
Headers
Response
Successful Response
Changes
No recorded changes to this operation across all 1 revision of this API.