zainar-halo-agent-tools
FastMCP server exposing ZaiNar RF halo awareness to LLM agents and Claude Desktop.
Gives an agent the ability to ask "what's around robot amr-7 right now?" and get a live answer — entity types, 3D ranges (cm), closing speeds — sourced from ZaiNar's RF network, not from cameras or line-of-sight sensors.
Install
pip install zainar-halo-agent-tools
Run the MCP server
zainar-halo-mcp
Add to Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json):
{
"mcpServers": {
"zainar-halo": { "command": "zainar-halo-mcp" }
}
}
Inspect interactively:
npx @modelcontextprotocol/inspector zainar-halo-mcp
Tools
| Tool | What it does |
|---|---|
get_halo(device_id) |
Rich egocentric halo — who's around this node, ranges, closing speeds |
set_halo_config(device_id, ...) |
Set safety perimeter and entity filters (operator-owned) |
query_near(device_id, radius_cm, entity_types) |
Ad-hoc proximity query, no persistent config change |
list_tracked_entities() |
All tracked entities with 3D positions and freshness |
list_zones() |
Active zones and entity counts |
get_zone_entities(zone) |
Raw TMI position list for a zone |
Resources
| URI | What it returns |
|---|---|
zainar://halo/{device_id} |
Live halo JSON for a node |
zainar://zone/{zone} |
TMI position list for a zone |
zainar://entities |
All tracked entities |
Demo vs. production
The out-of-the-box server uses DemoLocationService — a fixed set of 6
demo positions (warehouse scenario with AMR, forklift, human, drone).
In production, swap it for ZainarLocationService from the
zainar-location-service package, which connects to the kinesis-gw
WebSocket and maintains a live position queue. The tool signatures are
identical.
See also
zainar-halo— the robot client lib this package builds onCLAUDE.mdat repo root — full architecture and integration guide
Metadata
Release files for zainar-halo-agent-tools 0.1.4
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 |
|---|---|---|---|---|
| zainar_halo_agent_tools-0.1.4.tar.gz | 17.7 kB | Without provenance | Details for zainar_halo_agent_tools-0.1.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| zainar_halo_agent_tools-0.1.4-py3-none-any.whl | Python 3 | none | any | Details for zainar_halo_agent_tools-0.1.4-py3-none-any.whl |
Total release size: 38.5 kB
Release files / zainar_halo_agent_tools-0.1.4.tar.gz
| Download URL | zainar_halo_agent_tools-0.1.4.tar.gz |
|---|---|
| Size | 17.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
eed9f3c0da4bfb158d9865ea07460c5b505732774f56a47f8a9cedff335ab442
|
|
BLAKE2b-256 checksum How to use checksums |
fa35800e4fb6722b9046a3d05585aca7b73af1c452e9c1750e16d2967dd682b9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.13
|
Release files / zainar_halo_agent_tools-0.1.4-py3-none-any.whl
| Download URL | zainar_halo_agent_tools-0.1.4-py3-none-any.whl |
|---|---|
| Size | 20.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
11aeadbeba45ad6bfccff6ffb1bb4dd08c6037f7392885e73768f3ed92d6beb0
|
|
BLAKE2b-256 checksum How to use checksums |
58a67a294104b877d35be5f33b6f9bdf8a07523f603c542af65be7797fe33e13
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.13
|
Security for zainar-halo-agent-tools 0.1.4
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.