Apps and Tools

OOMOL uses two stable terms for agent access:

• Apps are the products and services connected to OOMOL, such as Gmail, Slack, GitHub, Notion, Linear, internal APIs, databases, files, or model providers.
• Tools are the callable capabilities agents invoke through OOMOL. One App can expose many Tools, such as reading email, creating an issue, posting a message, searching files, or running a custom function.

This separation keeps the product model clear. People connect Apps. Agents call Tools.

How this maps to OOMOL

When you connect an App account, OOMOL stores the account, authorization, permissions, usage, and execution records in one place. Agents do not need raw tokens for that App. They call approved Tools through OOMOL instead.

Skills sit above Tools. A Skill preserves the working method around one or more Tools: which Tool to call, what context to include, what constraints to follow, and how to check the result.

Implementation terms

Some lower-level commands and APIs use connector action as the precise execution-layer term. For example, the CLI namespace is still oo connector:

oo connector search "send an email"
oo connector schema <serviceName> -a <action>
oo connector run <serviceName> -a <action> --data @input.json

In user-facing copy, you can describe what agents call as Tools. In CLI, schema, logs, JSON fields, and API parameters, use connector action when that is the exact object being documented.