Tools
Tools extend what your agents can do beyond conversation. With tools, agents can remember information, make calculations, call APIs, and interact with external services.
What Are Tools?
Think of tools as the hands and eyes of your agent. Without tools, an agent can only talk. With tools, it can actually do things -- look up an order, create a ticket, send an email, or query a database.
When an agent decides it needs to use a tool, it:
- Chooses which tool to use based on the conversation
- Provides the required inputs
- Receives the tool's output
- Uses that output to craft its response
Tool Categories
Built-in Tools
MeetLoyd provides several tools out of the box:
| Tool | What It Does |
|---|---|
| Memory | Store and retrieve information across conversations |
| Calculator | Perform mathematical calculations (arithmetic, percentages, compound interest) |
| Current Time | Get the current date and time in any timezone |
Integration Tools
When you connect an integration in Settings > Integrations, its tools automatically become available to your agents. No extra configuration needed -- just connect and go.
| Integration | Tools Available |
|---|---|
| GitHub | 67 operations across repos, issues, PRs, actions, security, projects, and discussions |
| HubSpot CRM | 17 operations: contacts, companies, deals, tickets, search, pipelines |
| Google Workspace | User management, groups, shared drives, and licenses |
| Microsoft 365 | User management, groups, Teams channels, SharePoint sites, and licenses |
Each connected integration exposes a single tool with an operation parameter. For example, GitHub becomes one github tool -- the agent selects the operation (e.g., search_repositories, create_issue) via the operation field. This keeps the total tool count low even with many integrations connected.
Platform Tools
Agents can interact with the MeetLoyd platform itself -- listing agents, creating tasks, getting workspace information, and more. These are especially useful for Loyd and other administrative agents.
How Tools Are Assigned
Tools are assigned to agents through authorization grants on the Authorization page. When you grant a permission (e.g., "Contributor" on a Git repository), the associated tools become available automatically.
You can also assign tools in the Agent Wizard when creating or editing an agent -- the "Access and Permissions" step lets you configure grants visually.
Structured Retry Strategies
Tools can define per-error retry guidance that tells agents exactly what to try when something fails. Instead of generic "try again" messages, agents receive targeted instructions like "Target agent not found. Use get_reachable_agents to find valid IDs."
When a tool fails, the platform matches the error against the tool's defined patterns, returns specific guidance, and suggests a fallback tool if one is configured.
Agents also learn from past mistakes. The platform tracks feedback and failure patterns, and injects "lessons learned" into agent prompts so they don't repeat the same errors across runs.
Connecting Integration Tools
- Go to Settings > Integrations in the dashboard
- Find the service you want to connect (GitHub, HubSpot, Google, etc.)
- Click Connect and complete the OAuth flow
- The integration's tools are now available to all agents in the workspace
GitHub
Full access to repositories, issues, pull requests, actions, code security, and more via the official GitHub MCP server.
| Category | Operations |
|---|---|
| Repositories | search, get file contents, create/update files, push, create repo, fork, branches, commits, code search |
| Issues | list, search, read, write, comment |
| Pull Requests | list, search, read, create, update, merge |
| Actions and CI | list, get, trigger, get job logs |
| Security | code scanning, secret scanning, Dependabot alerts |
| Projects | list, get, write |
| Discussions | list, get, get comments |
HubSpot CRM
| Category | Operations |
|---|---|
| Contacts | list, get, create, update |
| Companies | list, get, create |
| Deals | list, get, create, update |
| Tickets | list, create |
| Search | cross-object search, associate records |
| Pipelines | list pipelines, list owners |
Google Workspace Admin
10 operations: user management, groups, shared drives, and licenses.
Microsoft 365 Admin
14 operations: user management, groups, Teams channels, SharePoint sites, and licenses.
Configuring Tool Access
Security Best Practices
| Practice | Description |
|---|---|
| Minimal tools | Only enable the tools each agent actually needs |
| Domain restrictions | Restrict which URLs HTTP tools can access |
| Environment variables | Never hardcode API keys -- use environment references |
| Rate limiting | Control how often tools can be called per time window |
| Timeouts | Set execution time limits to prevent hanging requests |
Guiding Tool Selection
Help agents know when to use tools by including guidance in the system prompt:
When to use the lookup_order tool:
- When a user asks about order status
- When a user provides an order number
When NOT to use tools:
- Simple greetings and conversation
- Questions you can answer from knowledge
Error Handling in Prompts
Tell agents how to behave when tools fail:
If a tool fails:
- Acknowledge the issue to the user
- Try an alternative approach if available
- Offer to create a ticket for manual resolution
- Never make up data or guess
MCP (Model Context Protocol)
For custom integrations, MeetLoyd supports the Model Context Protocol. You can connect any MCP-compatible server to give agents access to your own APIs, databases, or internal tools.