list_council
Lists every council member's id, label, model, weight, endpoint, call budget, and readiness, so you know which ids to use with ask/ask_all or can spot configuration issues.
Instructions
List the council's members: their ids, labels, target models, weights, wire format, endpoint, call budget, and whether each one is ready to answer.
weight is how much this council trusts each member, relative to the others;
everyone is 1 unless the roster says otherwise, and ask_all reports it
alongside the answers whenever they differ.
tries is how many attempts a call gets and how long each may take, so a
member that is slow or that keeps being retried is visible here.
sees is whether this member may be shown an image in materials. The line
above the table says whether this server will read materials paths at all,
which depends on how its operator runs it.
route is how this member reaches its endpoint — env follows the proxy in
the server's environment, direct ignores it, and a URL is a proxy set for
that member alone. It appears only when the members can differ; passwords in
a proxy URL are masked.
A member may have backups: further endpoints for the same seat, indented
under it as ↳ backup 1, ↳ backup 2 and tried in that order when the one
above does not answer. They are the same member — same id, same label, one
vote — so you never address a backup directly; the seat's id reaches
whichever of them is up. Read their model column: a backup is often the
same model under a different id, and sometimes not the same model at all,
and ask_all names the one that actually answered above each answer.
Cheap and local — makes no network calls. Use this to find out which ids you
may pass to ask and ask_all, or to explain a configuration problem.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |