post_v1_captable_rounds_id_close
CloseRound closes one of the caller org's fundraising rounds, recording the close date and moving its status to CLOSED.
CloseRound closes one of the caller org's fundraising rounds, recording the close date and moving its status to CLOSED. Only an OPEN round can be closed: a round that is already closed — like an id this org does not hold — is not found. Closing a round does not change what was invested in it.
| Tool | post_v1_captable_rounds_id_close |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 2 |
| Operation | POST /v1/captable/rounds/{id}/close |
| Product | captable |
Arguments
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
closeDate | any | — | — | CloseDate is the date to record the round as closed on. Optional: omitted, null or empty records TODAY. Any JSON scalar is accepted and stored as its text, and the text is stored unparsed, so a caller that wants an ISO date sends one. |
id | string | — | — | ID is the round to close. It is the path segment: the URL is the addressing authority, and the org it is resolved in comes from the caller's principal, so an id from another tenant is simply not found. |
This tool's schema does not declare which fields are required, nor any default, nor any enumerated value set. The columns above are empty because the door publishes nothing there, not because the answer is "none" — where a field is constrained, the constraint is stated in that field's own description.
Call it
A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Every declared argument is shown, because the door marks none of them required.
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": "post_v1_captable_rounds_id_close",
"arguments": {
"closeDate": "<closeDate>",
"id": "<id>"
}
}
}'Values are placeholders derived from each field's declared type. 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 |
|---|---|---|---|
cloud_post_v1_captable_rounds_id_close | POST /v1/captable/rounds/{id}/close | captable | CloseRound closes one of the caller org's fundraising rounds, recording the close date and |
The same capability over plain HTTP is in the captable API reference, on https://api.hanzo.ai.
All 834 tools · The door · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 834 tools captured 2026-08-01 (this build read the vendored copy; the door was unreachable).
How is this guide?