get_v1_agents_builds_org_project
ReadBuild returns the readable build of one product: the agent session that produced it, turn by turn — the prompts, the reasoning, the commits each turn produced — plus the exact `git log` that…
ReadBuild returns the readable build of one product: the agent session that
produced it, turn by turn — the prompts, the reasoning, the commits each turn
produced — plus the exact git log that re-derives every commit binding from
git itself, so nothing here has to be taken on trust.
PUBLIC, no tenancy: it answers only for a session its author explicitly published, which is what makes it safe to be anonymous. An unpublished session is invisible here no matter who asks; its owner reads it through the org-scoped /v1/agents/sessions routes, which need a validated principal.
| Tool | get_v1_agents_builds_org_project |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 2, 2 required |
| Operation | GET /v1/agents/builds/{org}/{project} |
| Product | agents |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
org | string | yes | — | — | Org is the org that published the build, from the path. |
project | string | yes | — | — | Project is the product's slug, from the path. |
tools/list declares a type and a description for each field and nothing further. The Required column is taken from GET /v1/agents/builds/{org}/{project}, the operation this tool dispatches to — the same declaration the REST API validates against. A — means neither the door nor that operation constrains the field.
Call it
A tools/call carries every argument in one flat object — nothing binds to a path or a query string. This call carries exactly the arguments the operation requires, so it is the smallest one that can run.
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "get_v1_agents_builds_org_project",
"arguments": {
"org": "<org>",
"project": "<project>"
}
}
}'Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. tools/list needs no credential; tools/call does — called without one the door answers HTTP 200 with a JSON-RPC result whose isError is set and whose text says what was missing. How to get a key →
The operation behind it
| Operation | Route | Product | Summary |
|---|---|---|---|
get_v1_agents_builds_org_project | GET /v1/agents/builds/{org}/{project} | agents | Returns the readable build of one product: the agent session that produced it, turn by… |
The same capability over plain HTTP is in the agents API reference, on https://api.hanzo.ai.
All 755 tools · The door · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 833 tools captured 2026-08-01, of which 755 are documented here (the operator surface is not published) (this build read the vendored copy; the door was unreachable).
How is this guide?