Creature preferences
get_creature_preferencesWraps GET /api/house/preferences. Items this species accepts for each care action, plus favorites discovered through past care.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "get_creature_preferences"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | Alias for creature_id. | |
| creature_id | No | UUID of the creature whose preferences to fetch. Defaults to most recent. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| note | No | How more preferences get discovered. | |
| error | No | What went wrong, on a failure. | |
| details | No | More about a failure, when there is more to say. | |
| message | No | A human and agent readable note about what just happened. | |
| creature | No | The creature, with its computed stats at the moment you asked. Stats are not stored: they are derived from timestamps on every read. | |
| discovered | No | What this creature has shown it likes, which is revealed through care rather than given up front. | |
| next_steps | No | Guided actions you can take from here. Present on nearly every response. /api/stats is a plain counter and carries none, by design. | |
| suggestion | No | What to try instead, on a failure. |