{"title":"Analyze MCP server tool calls telemetry","url":"https://jonas-paprotka.de/docs/dev-itpro/administration/telemetry-mcp-server-trace/","by":"JOP-AL","license":"Copyright (c) Microsoft Corporation. CC BY 4.0, https://creativecommons.org/licenses/by/4.0/; code samples MIT. From https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/telemetry-mcp-server-trace, MicrosoftDocs/dynamics365smb-devitpro-pb at 828b6ee (2026-11-19). Changed: includes filled in, links to this site, and for agents shortened without dropping a fact.","credit":"Microsoft Corporation, CC BY 4.0","origin":"https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/telemetry-mcp-server-trace","source":{"name":"Business Central developer and IT pro docs","repo":"https://github.com/MicrosoftDocs/dynamics365smb-devitpro-pb","commit":"828b6ee72fcd75755627cd6011f3d20899217ab2","date":"2026-11-19"},"checked":"2026-11-19","description":"Analyze Business Central MCP server tool call telemetry to track tool usage, investigate invocation failures, and compare performance across configurations.","date":"2026-11-17","meta":{"topic":"concept-article"},"outline":[{"level":1,"title":"Analyze MCP server tool calls telemetry","slug":"analyze-mcp-server-tool-calls-telemetry","at":0,"chars":5822},{"level":2,"title":"MCP server tool called","slug":"mcp-server-tool-called","at":462,"chars":4762},{"level":3,"title":"General dimensions","slug":"general-dimensions","at":557,"chars":314},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions","at":871,"chars":1717},{"level":3,"title":"Sample KQL code","slug":"sample-kql-code","at":2588,"chars":854},{"level":3,"title":"Sample KQL code for failed tool invocations","slug":"sample-kql-code-for-failed-tool-invocations","at":3442,"chars":841},{"level":3,"title":"Sample KQL code for tool usage by configuration","slug":"sample-kql-code-for-tool-usage-by-configuration","at":4283,"chars":941},{"level":2,"title":"Related information","slug":"related-information","at":5224,"chars":598}],"text":"# Analyze MCP server tool calls telemetry\nAPPLIES TO: Business Central 2026 release wave 1, version 28.0, and later\nModel Context Protocol (MCP)<../ai/mcp-overview> server telemetry gathers data about calls that external MCP hosts make to tools exposed by Business Central MCP server configurations. This telemetry helps you understand how external clients use Business Central through MCP.\nSee Configure Business Central MCP Server<../ai/configure-mcp-server>.\n## MCP server tool called\nOccurs when Business Central processes a tool call from an MCP host.\n### General dimensions\nDimension|Description or value\nmessage|MCP Server tool called: '{toolName}'\nuser_Id|The user telemetry ID for the user. From the user card, you can use user_Id to identify the user who triggered this telemetry event. See telemetry-enable-application-insights#assign-a-telemetry-id-to-users.\n### Custom dimensions\nDimension|Description or value\naadTenantId|Specifies the Microsoft Entra tenant ID used for Microsoft Entra authentication. For on-premises, if you aren't using Microsoft Entra authentication, this value is common.\ncompanyName|The current company name.\nenvironmentName|Specifies the name of the tenant environment. See Managing Environments<tenant-admin-center-environments>.\nenvironmentType|Specifies the environment type for the tenant, such as Production or Sandbox. See tenant-admin-center-environments#types-of-environments.\neventId|RT0054\nconfigurationName|Specifies the name of the MCP configuration that was used for the tool call.\nconfigurationSystemId|Specifies the system ID (GUID) of the MCP configuration record.\ntoolName|Specifies the name of the MCP tool that was called.\ndynamicToolName|Specifies the action name for dynamic MCP tools. This dimension is populated when using dynamic tool configurations.\nclientName|Specifies the name of the MCP host that initiated the tool call.\nauthAppId|Specifies the authenticated application ID from the security token.\nresult|Specifies the result of the operation. Possible values are Success or Failure.\ntotalTime|Specifies the total time the operation ran for.\nserverExecutionTime|Specifies the amount of time the operation took on server. The time has the format hh:mm:ss.sssssss.\ntoolInvocationResult|Specifies the result of the MCP tool invocation. Possible values are Success or Failure. This dimension can be absent if an exception prevents the tool call from returning a result.\ntoolInvocationFailureReason|Specifies the reason for the tool invocation failure. This dimension is only populated when toolInvocationResult is Failure.\n### Sample KQL code\nThis KQL code can help you get started analyzing MCP Server tool calls:\n```kql\ntraces\n| where timestamp > ago(60d) // adjust as needed\n| where customDimensions.eventId == 'RT0054'\n| project timestamp\n, aadTenantId = customDimensions.aadTenantId\n, environmentName = customDimensions.environmentName\n, environmentType = customDimensions.environmentType\n, companyName = customDimensions.companyName\n, configurationName = customDimensions.configurationName\n, toolName = customDimensions.toolName\n, dynamicToolName = customDimensions.dynamicToolName\n, clientName = customDimensions.clientName\n, toolInvocationResult = customDimensions.toolInvocationResult\n, toolInvocationFailureReason = customDimensions.toolInvocationFailureReason\n, totalTime = customDimensions.totalTime\n, serverExecutionTime = customDimensions.serverExecutionTime\n```\n### Sample KQL code for failed tool invocations\nThis KQL code can help you analyze failed MCP Server tool calls:\n```kql\ntraces\n| where timestamp > ago(60d) // adjust as needed\n| where customDimensions.eventId == 'RT0054'\n| where customDimensions.toolInvocationResult == 'Failure'\n| project timestamp\n, aadTenantId = customDimensions.aadTenantId\n, environmentName = customDimensions.environmentName\n, environmentType = customDimensions.environmentType\n, companyName = customDimensions.companyName\n, configurationName = customDimensions.configurationName\n, toolName = customDimensions.toolName\n, clientName = customDimensions.clientName\n, toolInvocationFailureReason = customDimensions.toolInvocationFailureReason\n| summarize FailureCount = count() by tostring(toolName), tostring(toolInvocationFailureReason)\n| order by FailureCount desc\n```\n### Sample KQL code for tool usage by configuration\nThis KQL code can help you understand which MCP configurations and tools are being used most frequently:\n```kql\ntraces\n| where timestamp > ago(30d) // adjust as needed\n| where customDimensions.eventId == 'RT0054'\n| summarize\n    TotalCalls = count()\n  , SuccessfulCalls = countif(customDimensions.toolInvocationResult == 'Success')\n  , FailedCalls = countif(customDimensions.toolInvocationResult == 'Failure')\n  , AvgServerExecutionTimeInMs = avg(toreal(totimespan(customDimensions.serverExecutionTime)) / 10000)\n  by\n    ConfigurationName = tostring(customDimensions.configurationName)\n  , ToolName = tostring(customDimensions.toolName)\n  , ClientName = tostring(customDimensions.clientName)\n| extend SuccessRate = round(100.0 * SuccessfulCalls / TotalCalls, 2)\n| order by TotalCalls desc\n```\nTo learn more about how to set up alerting on Business Central telemetry, see telemetry-alert.\n## Related information\nModel Context Protocol (MCP) in Business Central overview<../ai/mcp-overview>\nConfigure Business Central MCP Server<../ai/configure-mcp-server>\nConnect to Business Central MCP Server with Visual Studio Code<../ai/use-mcp-server-in-vscode>\nConnect to Business Central MCP server with non-Microsoft clients<../ai/use-mcp-server-non-microsoft>\nBusiness Central Admin Center API MCP server<administration-center-api-mcp>\nMonitoring and Analyzing Telemetry<telemetry-overview>\nEnable Sending Telemetry to Application Insights<telemetry-enable-application-insights>\ntelemetry-alert"}