Trigger Event
msfs_trigger_eventFire any SimConnect event by name with optional parameter. Resolves official and third-party events via catalog or direct mapping, confirmed by send ID.
Instructions
Fire a SimConnect event.
Resolves through the library's 994-event catalog first, then falls back to mapping the name directly, so third-party and newer MSFS events work too. Either way, the event is sent through the same MapClientEventToSimEvent + TransmitClientEvent pair, correlated by send ID on a dispatcher-equipped connection (NAME_UNRECOGNIZED/ERROR mean the event doesn't exist; other exceptions propagate as errors).
That correlation proves SimConnect accepted the packet -- not that the
aircraft acted on it. An aircraft with its own event system (PMDG, Fenix)
can silently ignore an event it received in favour of its own SDK; see
message and CLAUDE.md's "Known Sim Behaviours".
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"name": "<name>"
},
"name": "msfs_trigger_event"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Event name, e.g. 'PARKING_BRAKES', 'AP_MASTER', 'THROTTLE_SET' | |
| parameter | No | Integer parameter for events that take one. Negative values are supported (e.g. AP_VS_VAR_SET_ENGLISH). |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |