Tools

Tools are how Agent / Workflow / Chatflow call external capabilities. Evose supports three sources, all under unified RBAC + ACL.

Three Tool Sources

Source	What it is	When to use
MCP	Model Context Protocol	Preferred. Rich ecosystem, easy to integrate
HTTP plugin	Configure a RESTful API's auth + schema	Plug in when you have an existing internal API
EvoTool marketplace	Out-of-the-box tools maintained by Evose and the community	Common tools (stock quotes, send email, maps)

4 Add Entries

Workspace → Capabilities · Tools → Add (org-level uses the same menu at Layer 3):

Entry	Input
Add MCP	URL / launch command + auth (optional)
Add Plugin	API endpoint + auth + Schema (JSON Schema)
From Marketplace	Pick from EvoTool and configure parameters
From Template	Pick a pre-configured tool from the template library

Add an MCP Tool (Recommended)

Name: Company CRM
URL:  http://crm.internal/mcp
Auth: Bearer + {{credential:crm_token}}
Description: Query customers, orders, contracts

After integration, the system auto-discovers all methods exposed by the MCP server, and you can tick them in Agent configuration.

Tool Card Information

Each tool card shows:

Field	Description
Method count	Total methods exposed by the tool
References	How many Agents / Workflows use it
Authorized workspaces (org-level)	How many workspaces are authorized
Status	Online (available) / Offline (failed, needs reconnect)

Workspace Tool vs Organization Tool

	Workspace Tool	Organization Tool
Where registered	Inside one workspace	Org management
Visibility	This workspace only	Visible in authorized workspaces
Who registers	Workspace admin	Org admin
Best for	Temporary experiments / private APIs	Company-wide shared (CRM / ERP / CS system)

→ Organization tool governance

Authorization Scope (Org Tools)

Org tools default to visible in all workspaces. Restrict scope for sensitive tools:

Tool: Production DB write
Authorized: ☑ workspace-prod
            ☐ workspace-staging
            ☐ workspace-dev

Use in Agent / Workflow

In Agent

Edit Agent → Tools tab → tick the tools to use
Tell the LLM when to use in the role prompt:
For customer-related questions: - Use the "Company CRM" tool to look up customer info - Use the "Order System" tool for order status
The LLM will function-call automatically based on the user's question

In Workflow / Chatflow

Drag a Tool node → pick the tool + method → explicitly map inputs → store output to a variable.

Credentials

Almost every tool requires credentials (API key / OAuth token / cookie). Don't hardcode them in tool config; instead:

Register the credential in Org · Security · Credentials (field-level encryption + audit)
In tool configuration, reference it via placeholder: {{credential:crm_token}}

→ Credential management

Observability of Tool Calls

Every tool call enters the Trace:

Agent.run
├─ tool_call: CompanyCRM.queryCustomer
│   ├─ input: {customer_id: "C001"}
│   ├─ duration: 234ms
│   ├─ status: ok
│   └─ output: {name: "...", orders: [...]}
└─ llm.complete(...)

→ Observability

Anti-Patterns

Stuffing business logic into a tool — a tool should be the thinnest layer of RPC; business logic lives in Workflow / Agent prompts
Hardcoding credentials in tool config — always go through credential management
Binding 50 tools to one Agent — the LLM gets confused when picking; recommend ≤ 10, clearly categorized

Next Steps

Skills → Skill
Register at org level → Organization tool
Configure credentials → Credential management

Tools (MCP / HTTP / EvoTool)