Basic Tool
Define a tool with the@tool decorator. Tools are served via the Model Context Protocol (MCP) and can be discovered and called by any MCP-compatible client.
The @tool Decorator
Tool name. Defaults to the function name.
Tool description. Defaults to the first paragraph of the function’s docstring.
Tags for filtering and organization.
Additional metadata as key-value pairs.
Schema from Type Hints
Input schema is automatically generated from function parameters. Type hints, default values, and docstring parameter descriptions are all captured.Docstring formats supported: Google style, NumPy style, and Sphinx style. Parameter descriptions from any of these formats are extracted into the schema’s
description field.Output Schema
Return type hints are also converted to an output schema.Context Parameter
Tools can receive execution context to access caller identity and metadata.Sync Tools
Synchronous functions are also supported. They are wrapped in async internally by the runtime.Serving Tools with Agents
Tools and agents can be served from the same process. Agents get their own REST endpoints and tools are served via MCP.MCP compatibility
When deployed, your tools are automatically served via the Model Context Protocol (MCP). Any MCP-compatible client — including Claude Desktop, custom MCP clients, and other Reminix agents — can discover and call your tools.MCP is an open standard for connecting AI models to tools and data sources. Your Reminix tools work with any client that speaks MCP.
Next steps
Tools (concept)
How tools become MCP servers and how clients discover them.
Connecting MCP clients
Add your tools to Claude Desktop, Cursor, and Windsurf.
Creating Agents
Define agents that call your tools internally.
Deploying
Ship your tools to production.