mirror of
https://github.com/hanzoai/python-sdk.git
synced 2026-10-23 20:23:00 +00:00
zeekay
9f6663482d
The rebase folded the fleet-wide projection into the newer v8.5.151 already on main, and two files did not survive it: git_api and websearch_api still described the previous emission. .spec-lock came back conflicted from the same rebase and is set to the document these were generated from. `generate.py python --check` is clean after.
36 lines
1.2 KiB
Python
36 lines
1.2 KiB
Python
"""tools — list the tools this key can reach.
|
|
|
|
``GET /v1/tools`` (operationId ``get_tools``), the catalog behind the
|
|
MCP surface: each entry is a tool name, its description and its input schema.
|
|
|
|
A note on the MCP endpoints, because it is easy to pick the wrong one. There is a
|
|
JSON-RPC endpoint at ``POST /v1/mcp`` that answers ``tools/list`` with the same
|
|
catalog — but it is NOT in the document, so the generator emits no method for it
|
|
and an example would have to bypass the SDK to call it, which defeats the point
|
|
of an SDK example. Of the MCP routes that ARE declared, ``/v1/automations/mcp``
|
|
404s at api.hanzo.ai. So this catalog read is the one that is both generated and
|
|
served. When ``/v1/mcp`` is added to the spec, this flow should move to it.
|
|
|
|
python -m examples.tools
|
|
"""
|
|
|
|
from hanzoai.cloud import ToolsApi
|
|
|
|
from examples.client import client, run
|
|
|
|
|
|
def main() -> None:
|
|
with client() as api:
|
|
catalog = ToolsApi(api).get_tools()
|
|
|
|
tools = catalog.tools or []
|
|
print(f"{len(tools)} tools")
|
|
for tool in tools[:20]:
|
|
print(f" {tool.name} — {tool.description or '(no description)'}")
|
|
if len(tools) > 20:
|
|
print(f" … and {len(tools) - 20} more")
|
|
|
|
|
|
if __name__ == "__main__":
|
|
run(main)
|