Every connection has these tools, with any access you grant. Your assistant sees them as soon as it connects.
list_tool_groups, search_tools,
describe_tools and use_tool find and run the tools in the groups you granted.
What your assistant is told about this group
Every connection has these tools, whatever you granted: the everyday lookups, and the four tools your assistant uses to find and run the tools in each group.
The descriptions below are the ones your assistant reads, so they're written for it. When a connection covers more than one
organisation, the assistant passes org (the organisation's slug, from list_orgs) to say which one.
list_orgs
Read List organisations
List the organisations this authorization may act in. When more than one is granted, pass an organisation's slug as the org argument to the other tools.
Arguments
None.
list_products
Read List insurance products
List an organisation's insurance products, optionally filtered by product_type or lifecycle_state. Each product includes its versioned sale terms (cooling-off, inclusions/exclusions, cover bounds) and covers.
Arguments
| Field | Type | Description |
|---|---|---|
| org | string | Organisation slug: required when this authorization covers more than one organisation (see list_orgs) |
| product_type | string |
Only return products of this type
One of: "term", "decreasing_term", "whole_of_life", "critical_illness", "income_protection", "bundled", "child_cover", "healthcare"
|
| lifecycle_state | string |
Only return products in this lifecycle state
One of: "draft", "sandbox", "production", "archived"
|
get_product
Read Get an insurance product
Fetch one insurance product by id, including its versioned sale terms (cooling-off, inclusions/exclusions, cover bounds) and covers.
Arguments
| Field | Type | Description |
|---|---|---|
| id required | string | Product id (UUID), as returned by list_products |
| org | string | Organisation slug: required when this authorization covers more than one organisation (see list_orgs) |
get_draft_changes
Read Get unpublished changes
What publishing the product's next release would change: each item that differs from the live release (the product, its covers, journeys, questions, presentations, documents and lifecycle events), with its draft and live versions, the changes field by field, and whether its draft can be discarded. Covers without a rule pack show as excluded, because they can't be released yet.
Arguments
| Field | Type | Description |
|---|---|---|
| product_id required | string | |
| org | string | Organisation slug: required when this authorization covers more than one organisation (see list_orgs) |
search_support
Read Search the Help center
Search Subcontext's Help center: how-to articles about using the platform (the dashboard's pages, what things mean, how to do things). Use it to explain how something works or where to find it. Returns titles and summaries; read one with get_support_article.
Arguments
| Field | Type | Description |
|---|---|---|
| query required | string | What you want to know, e.g. "lead stages" or "archive a lead" |
get_support_article
Read Read a Help center article
Read one Help center article in full (markdown), by the slug search_support returned.
Arguments
| Field | Type | Description |
|---|---|---|
| slug required | string |
diagnose_account
Read Check the account for problems
Check the organisation's account for what's stopping things working, most serious first: subscription and AI credit, channels that can't send (WhatsApp sender offline, no number), phone compliance, rejected or paused WhatsApp templates, sending domains, email bounces and complaints, integrations that can't sign in, failing workflows and undelivered messages. Each finding has a Help center article (help_slug) and the page to fix it on (path). Use it first when someone says something isn't working.
Arguments
| Field | Type | Description |
|---|---|---|
| org | string | Organisation slug: required when this authorization covers more than one organisation (see list_orgs) |
get_whats_new
Read What's new
Catch up on everything that has happened, in one call. Use it first when someone asks what's new, what they missed, or how today is going. Returns: today's activity counts per area (escalations, conversations, bookings, sales, leads, automation) and today's newly bound premium; the latest customer and agent activity since `since`; how many escalations are open; the person's unread notifications; and, for managers, changes to the setup itself (settings, team, agents, products). Sections this person can't see are left out. since is an ISO 8601 date or time, default the last 24 hours. Follow up with list_crm_feed (more activity), list_my_notifications or list_org_audit_logs for detail.
Arguments
| Field | Type | Description |
|---|---|---|
| since | string | |
| org | string | Organisation slug: required when this authorization covers more than one organisation (see list_orgs) |
list_tool_groups
Finds and runs tools List tool groups
The tool groups available to this authorization beyond the always-on core. Each group bundles related operations: use search_tools or describe_tools(group:) to drill in, then use_tool to invoke.
Arguments
None.
search_tools
Finds and runs tools Search tools
Keyword-search the full tool catalogue (names + descriptions). Returns names and one-liners: call describe_tools for full schemas, or go straight to use_tool if the arguments are obvious.
Arguments
| Field | Type | Description |
|---|---|---|
| query required | string | e.g. "archive cover" or "publish" |
| group | string | Restrict to one group key (see list_tool_groups) |
describe_tools
Finds and runs tools Describe tools
Full input schemas for a tool group or a list of tool names, plus the group's workflow overview. Invoke the described tools with use_tool.
Arguments
| Field | Type | Description |
|---|---|---|
| group | string | A group key from list_tool_groups |
| names | array of string | Specific tool names |
use_tool
Finds and runs tools Invoke a tool
Invoke any tool from the catalogue by name (discover via list_tool_groups / search_tools; schemas via describe_tools). Arguments are validated against the target tool's schema exactly as a direct call would be.
Arguments
| Field | Type | Description |
|---|---|---|
| name required | string | Tool name, e.g. create_cover |
| arguments | object | The target tool's arguments |