get_v1_git_repos_name_files

Returns every file a glob selects at one revision, WITH its bytes and the revision they came from. It is the read a delivery generator makes: one call answers "what is the inventory at this commit, and what does it say", where listing and then fetching would be a request per file.

Returning the resolved revision matters as much as the bytes. A generator that lists at main and then reads at main can straddle a push and assemble half its inventory from one commit and half from the next; resolving once makes the whole read consistent by construction.

A file past the read cap comes back Truncated with no content rather than being dropped. A caller building a desired set has to know the difference between "this file is empty" and "this file was not read" — silently omitting it is how a pruning reconcile deletes what the missing file declared.

Arguments

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": "get_v1_git_repos_name_files",
         "arguments": {
           "glob": "<glob>",
           "name": "<name>",
           "ref": "<ref>"
         }
       }
     }'

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

The same capability over plain HTTP is in the git 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).