Meshagent
MeshAgent Tools
The meshagent.tools package bundles reusable tool and toolkit abstractions plus a set of out of the box MeshAgent toolkits.
ToolContext and BaseTool
The ToolContext tracks the caller and optional "on-behalf-of" participant. Tools that actually need a room should require a RoomToolContext or use a room-bound Toolkit. The BaseTool defines metadata used by all tools such as name and description.
Tool and Toolkit
A Tool encapsulates a single operation with an input JSON schema. Each tool implements an execute function where you define the logic for the tool. The Toolkit groups tools together and can enforce rules or descriptions.
Response Types
Response types specify the output that a tool should return. This helps the tool and agent know how to handle the response appropriately. Response types include: JsonChunk, TextChunk, and FileChunk.
from meshagent.tools import FunctionTool, Toolkit, ToolContext
from meshagent.api.messaging import TextChunk
class MyNewTool(FunctionTool):
def __init__(self):
super().__init__(
name="my_new_tool",
title="A sample tool",
description="The tool skeleton",
input_schema={
"type":"object",
"additionalProperties": False,
"required": [...],
"properties": {...}
}
)
async def execute(self, ctx:ToolContext, sample_parameter:str):
# tool logic
return TextChunk(text="Tool logic complete")
class MyNewToolkit(Toolkit):
def __init__(self):
super().__init__(
name="my_new_toolkit",
title="An example toolkit",
description="The toolkit skeleton",
tools=[MyNewTool])
Built-in Toolkits
Some of the built-in MeshAgent toolkits include:
StorageToolkit: Provides file operations (read, write, list, etc.)DocumentAuthoringToolkit: Defines tools for manipulating Mesh documents (create document, add element, remove element, etc.)
Learn more about MeshAgent on our website or check out the docs for additional examples!
Website: www.meshagent.com
Documentation: docs.meshagent.com
1 maintainer
Metadata
1 maintainer
Release files for meshagent-tools 0.55.0
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 | |
|---|---|---|---|---|
| meshagent_tools-0.55.0.tar.gz | 132.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| meshagent_tools-0.55.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 255.0 kB
Release files / meshagent_tools-0.55.0.tar.gz
| Download URL | meshagent_tools-0.55.0.tar.gz |
|---|---|
| Size | 132.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9b9ed98afbf06a9eb4d05f83b03ee4b424f0616b754d535cc0b5d8b47860948f
|
|
BLAKE2b-256 checksum How to use checksums |
8273cc86af8bf44e7873fa450e0617643ace709999b9fe99ce22902655451847
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / meshagent_tools-0.55.0-py3-none-any.whl
| Download URL | meshagent_tools-0.55.0-py3-none-any.whl |
|---|---|
| Size | 122.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
aa8a7207144b78592aa5b7625fc3172399315af71b4a64f29ab878696a1be393
|
|
BLAKE2b-256 checksum How to use checksums |
1a28151209f35800be12613fc1f1bcffdb0da52017b8a313418292d6db9b0a90
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Security for meshagent-tools 0.55.0
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.
