describe_endpoint
3 parameters and request shape
| Name | Type | Required |
|---|---|---|
| name | string | optional |
| endpoint | string | optional |
| endpointName | string | optional |
POST /api/describe_endpoint
{ ... }API reference
The complete surface: 717 Unreal Engine endpoints and 364 MifBlender operations, generated from the live registry (self_audit and describe_endpoint for Unreal, the addon’s operation tables for Blender). A name that does not exist cannot appear here, and each parameter list is the vocabulary that endpoint enforces.
2 matching entriespress / to search
edit_control_rig
'edit_control_rig' has NO ROW in describe_endpoint's harvested table, so its accepted parameter set is UNKNOWN HERE. acceptedParams is omitted rather than empty - this is 'unknown', NOT 'takes no parameters'. WHAT THIS DOES NOT TELL YOU: whether the handler guards its input. A missing row has TWO possible causes and this endpoint cannot tell them apart - (a) the handler calls no RejectUnknownParams, in which case it SILENTLY IGNORES any key it does not read, including a typo'd one; or (b) it does guard, and its guard was written after this table was harvested, in which case an unknown key is REJECTED and the whole call fails. Those outcomes are opposite, so do not assume either: read the handler body, or use the @mcp.tool signature in server.py as the nearest available contract. 1 of 717 registered endpoints have no table row. Parameters are NOT declared to MifBridge: this endpoint is registered by MifBridge, and an empty list here would mean 'takes none' rather than 'unknown'. Consult that provider.
0 parameters and request shape
Takes no parameters.
POST /api/edit_control_rig
{ ... }