Graph

graph: 14 operations.

Also for this capability: API · CLI · MCP · SDKs

graph: 14 operations. Name one in "op" and pass that operation's own arguments in "input". describe returns an operation's input schema.

Tool	`graph`
Address	`https://api.hanzo.ai/v1/mcp`
Method	`tools/call` (JSON-RPC 2.0)
Arguments	2, 1 required
Operation	`POST /v1/graph/answer` · `POST /v1/graph` · `POST /v1/graph/communities` · `POST /v1/graph/derive` · `POST /v1/graph/diff` · `POST /v1/graph/erase` · `POST /v1/graph/extract` · `POST /v1/graph/ingest` · `POST /v1/graph/neighbors` · `POST /v1/graph/path` · `GET /v1/graph` · `POST /v1/graph/resolve` · `GET /v1/graph/search` · `GET /v1/graph/vocabulary`
Product	graph

Arguments

Field	Type	Required	Default	Values	Description
`input`	`object`	—	—	—	arguments for the chosen op
`op`	`string`	yes	—	—	—

tools/list declares a type, a description, which fields are required and an enumerated value set for each field and nothing further, and every column above is MCP's own. This tool takes an operation name and that operation's arguments, so what the document constrains is what goes inside input, field by field, on the operation you name — ask describe for that. A — means MCP does not constrain 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": "graph",
         "arguments": {
           "op": "<op>"
         }
       }
     }'

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 MCP 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

graph dispatches to 14 operations.

Operation	Route	Product	Summary
`graphAnswer`	`POST /v1/graph/answer`	graph	Answers a question from the whole graph and cites the assertions it rests on.
`graphAssert`	`POST /v1/graph`	graph	Records a batch of assertions and counts what became of each.
`graphCommunities`	`POST /v1/graph/communities`	graph	Partitions the edge graph into sets of entities more densely connected to each other than to the rest.
`graphDerive`	`POST /v1/graph/derive`	graph	Concludes what the organization's rules derive from the graph, with a proof for every conclusion: the rule, and each support as the assertion in force it rests on or as the derived atom it is.
`graphDiff`	`POST /v1/graph/diff`	graph	Reports what came into force, was superseded and was retracted between two points.
`graphErase`	`POST /v1/graph/erase`	graph	Removes every assertion that names an entity and returns a receipt.
`graphExtract`	`POST /v1/graph/extract`	graph	Reads the relations a source states and returns them, recording nothing.
`graphIngest`	`POST /v1/graph/ingest`	graph	Reads a source and records what it states, through the same admission as assert.
`graphNeighbors`	`POST /v1/graph/neighbors`	graph	Walks the in-force edges from a set of seeds and lists every entity reached, bounded.
`graphPath`	`POST /v1/graph/path`	graph	Finds the shortest chain of in-force edges from one entity to another.
`graphRead`	`GET /v1/graph`	graph	Lists the assertions recorded, every version, oldest first.
`graphResolve`	`POST /v1/graph/resolve`	graph	Answers what holds for one entity and relation at a point, winner first, with every weaker account that disagreed.
`graphSearch`	`GET /v1/graph/search`	graph	Finds assertions by their words, where read finds them by their keys, best match first.
`graphVocabulary`	`GET /v1/graph/vocabulary`	graph	Lists the relations in use, the schema declared for them and the rule that settles a conflict.

The same capability over plain HTTP is in the graph API reference, on https://api.hanzo.ai.

All 120 tools · MCP · API reference

Generated from tools/list on https://api.hanzo.ai/v1/mcp — 120 tools captured 2026-09-30.

Was this page useful?

PreviousGit NextGuide