pub async fn list(__arg0: State<AppState>) -> impl IntoResponseExpand description
GET /v1/client-tools: every client-performed tool declaration this server
was started with.
This is how a client-driven loop gets the function definitions to hand the
model: a declaration’s input_schema IS the model tool’s parameter schema,
the same schema the server checks a client-tool intent’s input against, so
publishing it here is what keeps the client from keeping a second copy that
can drift from the one the server validates against.
No drive token: this is server configuration, not run state, so it sits
behind only the bearer-auth layer every other /v1 route sits behind.
Empty (never an error) on a server started with no --client-tool files,
the same honest-empty posture ClientToolRegistry itself takes.