| Term | Meaning |
|---|---|
| Application | An integrable product in the Engini catalog, identified by a slug (e.g. monday). |
| Connection | An authenticated link between your account and an application (integer id). Tools run through a connection. |
| Default connection | The per-application connection used when a tool call doesn’t specify one. |
| Tool | One executable action exposed by an application, identified by a slug (e.g. monday_create_item). |
| Toolset | A named bundle of connections + permitted tools (GUID id), typically handed to an LLM agent as its tool belt. |
| Object selection | For applications that expose selectable objects (e.g. database tables): choosing which ones the connection syncs. |
| Authentication method | A way to connect to an application (API key, OAuth2, credentials…), each with its own authenticationId and field list. |
isSuccess | The field on a tool-execute response that tells you whether the tool actually succeeded - a 200 alone does not. |
| Result handle | A CLI reference (h42) to a large tool result stored locally - drill in with engini tools result. |
Concepts
Glossary
Engini terminology.