MCP discovery tools
getActionsCatalog, getProviderActions, getAgentActions, chain capabilities, and MCP resources.
Use discovery tools to find out what your agent can do: which actions exist, which providers offer them, and which chains they run on. They only read, so run them before every write. The live catalog is always the source of truth.
Core discovery tools
| Tool | Purpose |
|---|---|
getActionsCatalog | Full public action catalog (providerFamilies, param schemas) |
getAgentActions | The actions one agent key may call, for its run mode (lane) |
getProviderActions | One provider's actions, with hints |
getChainCapabilities | Supported EVM chains, with run-mode (lane) details |
getNonEvmCapabilities | Solana and other non-EVM chains |
getProviderActions details:
| Input | Notes |
|---|---|
provider or providerId | Either name works; both take the same values |
view | concise or detailed |
limit, cursor | Page through long results |
It uses the API's providerFamilies when available.
Provider filters (integrator map)
Pass one of these values as provider to see that integration's actions.
| Filter | Integrations doc |
|---|---|
trading | Kyber |
hyperliquid | Hyperliquid |
avantis, avantis-vault | Veranta (formerly Avantis) |
polymarket, prediction | Polymarket |
earn, morpho, aegis, curve, vaults-fyi, yield-xyz, capyfi | Yield integrations |
bitfinex | Bitfinex |
bridge | Li.Fi |
dogeos-barkswap, dogeos-laika, dogeos-ecosystem | DogeOS |
allora | Allora |
nansen | Nansen |
fomo | Fomo API |
cmc | CoinMarketCap |
openmarket, openmarket-metrics | OpenMarket |
gmgn | GMGN |
basedbid | basedbid |
For every venue, see Integrations venues.
Typed toolsets
By default, your agent reaches the catalog through general tools: it looks up an action with getProviderActions, then runs it with agentRun. To give the model one tool per action, each with its own input fields, add ?toolsets= to the connector URL:
| Value | Adds |
|---|---|
A provider id (hyperliquid, polymarket, openmarket, cmc, ...) | That provider's actions |
A domain (perps, yield, prediction, ...) | Every action in that domain |
signals | The read-only data reads that publish signals. They return typed values, parse issues and freshness as structuredContent |
all | Everything your agent may call |
&readonly=1 | Keeps read-only tools only |
Good to know:
- Typed tools appear only on a connection that sends an agent key, and only for actions that agent may call.
- One connection gets at most 50 typed tools, so name only the providers you need.
verantaandveranta-vaultmap to theavantisandavantis-vaultproviders.
MCP resources
Hosts that read MCP resources can fetch the provider list and catalog directly. Each one also has a plain HTTP route.
| URI | HTTP |
|---|---|
thirdfy://providers | GET /resources/providers |
thirdfy://actions/catalog | GET /resources/actions/catalog |
Example sequence
A typical discovery pass before a Hyperliquid write:
Without MCP, the REST equivalent is GET https://api.thirdfy.com/api/v1/agent/actions/catalog.