Tools
What is a tool on Rival?
A tool on Rival is a callable unit of functionality. You define it once - code, inputs, configuration - and from then on it can be invoked from the Rival app at cortexone.rival.io, called over HTTP from your own services, or used by other tools and agents.
Everything else on the platform is built around tools: the Marketplace lists them, Analytics measures them, and the Mission Board is where the community asks for new ones.
The three tool types
Rival supports three tool types. You pick one when you create a tool, and it determines what kind of work the tool does.
- Function - a callable unit with structured inputs and outputs. Best for processing, transformation, and “input in, result out” logic.
- MCP - a server that exposes capabilities to AI agents and IDE assistants using the Model Context Protocol.
- Storm - a content classifier that tags incoming documents against a taxonomy you provide.
See Tool Types for a deeper comparison and guidance on when to pick each.
Where tools live
There are two places to find tools in the app:
- My Tools - every tool created inside your organization, including private drafts. Available from the left sidebar Nav once you sign in.
- Marketplace - public tools published by any organization. Open to everyone at cortexone.rival.io/marketplace.
In My Tools you see operational details for the tools your organization owns: total published tools, total runs, revenue generated, and a card for each tool that surfaces its type, visibility, current version, run count, revenue, and rating. From a tool card you can edit, delete, favorite, or view in Marketplace.
Versions
Every tool is managed through versions. A version is an immutable snapshot of the tool at publish time - the code, the input schema, the test cases, and the pricing - all frozen together.
Version numbers follow Semantic Versioning, and you pick the type of update when publishing:
- Patch - small fixes (
0.0.1 → 0.0.2) - Minor - backwards-compatible additions (
0.0.1 → 0.1.0) - Major - breaking changes (
0.0.1 → 1.0.0)
One version is shown on the top of a tool’s Marketplace listing - that’s the one callers reach by default. However, one can select the public version they want to run.
See Versions for the full model.
Visibility
A tool can be Private or Public.
Private tools are available only within your organization. They’re useful for internal workflows, integrations, or tools you’re still iterating on.
Public tools are listed in the Marketplace and callable by anyone with an account and wallet balance. Public tools require a pricing choice per version:
- Free - no charge to run beyond the standard run cost
- Paid - the publisher sets a per-run price on top of the standard run cost
- Private - listed for visibility but only callable by approved organizations
Creating a tool
A tool is created in the Tool Editor, where you set its basic info, write and test your code, add branding and documentation, and publish.
For a step-by-step walkthrough, see Creating a tool.
Tool lifecycle
A tool moves through three states:
- Draft - not published, not callable, not listed.
- Private - callable inside the organization, not listed in Marketplace.
- Public - listed in Marketplace, callable by anyone with an account.
Tools and versions can be deprecated (graceful 30-day removal with notifications to users) or deleted (immediate, permanent - only allowed when no public versions exist). See Deleting & Deprecating for the rules.
Favorites, or saving a tool
You can favorite any tool from My Tools or the Marketplace by clicking the bookmark icon on the top-right of its card. Saved or bookmarked tools are listed under the Favorites tab in My Tools - a place to keep the tools you use most, for quick access.