This release is a pre-release and may not be stable for production use.
Friday Tools
Tool definitions, registries, schema adapters, and a catalog of native and integration tools. Use it to expose typed Python functions to agents or to select built-in tools for your application.
Distribution: friday-framework-tools · Import: friday_tools
Python: 3.13.4+ · Status: alpha · License: MIT
Installation
python -m pip install "friday-framework-tools==0.1.0a4"
Friday distributions use the same release version; keep internal Friday dependencies aligned.
Quick start: define and invoke a tool
import asyncio
from friday_tools import DefaultToolRegistry, FunctionTool
def greet(name: str) -> str:
"""Return a greeting."""
return f"Hello, {name}!"
async def main() -> None:
tool = FunctionTool(greet)
registry = DefaultToolRegistry()
registry.register(tool)
print(registry.list_names())
print(await tool.execute(name="Friday"))
asyncio.run(main())
Expected output includes greet and Hello, Friday!. This invokes a local function directly; it does not call a model or register every built-in tool.
Catalog and integrations
Native categories include filesystem, shell, web, git, text, data, code and memory. get_default_registry() supplies the shared default registry; use a new DefaultToolRegistry when your application needs its own membership.
| Extra | Purpose |
|---|---|
sandbox |
Sandbox-backed execution integration |
finance, moltbook |
Corresponding provider integrations |
documents, spreadsheets, all-formats |
Optional file-format dependencies |
llm, langchain, anthropic, openai, all-adapters |
Schema/provider adapter dependencies |
For example: python -m pip install "friday-framework-tools[documents]==0.1.0a4". Extras install dependencies; applications still configure and admit tools explicitly. FunctionTool and the typed FridayTool/ToolResult surface have different result contracts; choose the one your caller expects.
Execution boundary
A registry and a generated JSON schema do not grant safe execution. Configure filesystem roots, shell restrictions, sandbox choice, tool selection and result sanitization in the owning application. External tools may access networks, incur charges, or mutate files. Read-only tools are the appropriate starting point for a new integration.
Development
Work from the monorepo root after the shared contributor setup. Run the focused suite:
uv run --no-sync pytest packages/friday-tools/tests_tools -q
Documentation and support
Tools guide · Security configuration · Sandbox backends · Source · Issues · Contributing
License
MIT.
Metadata
Release files for friday-framework-tools 0.1.0a4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| friday_framework_tools-0.1.0a4.tar.gz | 115.6 kB | Without provenance | Details for friday_framework_tools-0.1.0a4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| friday_framework_tools-0.1.0a4-py3-none-any.whl | Python 3 | none | any | Details for friday_framework_tools-0.1.0a4-py3-none-any.whl |
Total release size: 260.2 kB
Release files / friday_framework_tools-0.1.0a4.tar.gz
| Download URL | friday_framework_tools-0.1.0a4.tar.gz |
|---|---|
| Size | 115.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
89dc527229830e687ce9ccde7e44ffae07cf5cdf7aa1e3e79a526f40928354bb
|
|
BLAKE2b-256 checksum How to use checksums |
98e18bc65fe456d347c5994a96df2e43276c6420e5b4fed4a9ca7dbf91aef467
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.3 {"installer":{"name":"uv","version":"0.11.3","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / friday_framework_tools-0.1.0a4-py3-none-any.whl
| Download URL | friday_framework_tools-0.1.0a4-py3-none-any.whl |
|---|---|
| Size | 144.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
498daf87da69462fc648b6565cb16650d5028c2905377f048de917885fc47ba0
|
|
BLAKE2b-256 checksum How to use checksums |
692b16e9c8f0a8673d898ae855d73f670b957a0888200deb699c3b493cdb9608
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.3 {"installer":{"name":"uv","version":"0.11.3","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for friday-framework-tools 0.1.0a4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.