hub_resource_set
Create or update an infrastructure/topology entity with structured attributes and typed relationships, keeping resource data queryable instead of buried in prose.
Instructions
Create or update a resource — an infrastructure/topology entity: host, vm, service, endpoint, or provider. Structured attributes (type, address, os, provider, status) and typed relationships go in fields, NOT prose. Use this instead of describing infra inside a card digest.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"slug": "<slug>",
"by": "<by>"
},
"name": "hub_resource_set"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| by | Yes | who is writing | |
| os | No | ||
| slug | Yes | resource id, e.g. "myvm" or "board.hubd.net" | |
| type | No | host | vm | service | endpoint | provider | ... (open vocabulary) | |
| edges | No | typed relationships, merged with existing: {"runs_on":["hubd"],"depends_on":["postgres"]}. Values are target slugs. | |
| digest | No | one-line description (keep prose minimal) | |
| status | No | live | down | planned | retired | |
| address | No | ip / hostname / url, optional | |
| provider | No | libvirt | cloudflare | bare-metal | ... |