List target tool catalog
Look up the tools that the per-target monit-agent currently exposes for a given target_locator (host, mysql, …). Returns each tool’s name, description, and JSON-Schema input_schema. Pair with /monit/tools/invoke to drive AI-SRE tool calls.
Restrictions
Usage
- Use
target_locatorto identify the target;target_kindis optional and is inferred from current target routing when omitted. - If multiple kinds match the same locator, the response is HTTP 200 with
data.error.code = "ambiguous_target_kind"and atarget_kindslist — retry with an explicittarget_kind. - The catalog is a candidate capability view, not an execution guarantee. The target Agent may go offline between catalog and invoke, or local Agent policy may block individual tools at invoke time.
- Each tool entry exposes only
name,target_kind,description, andinput_schema. It does not expose tool versions, output contracts, catalog revisions, or execution limits. - Business errors (
target_unavailable,timeout,forward_failed,invalid_tool_result,ambiguous_target_kind) return HTTP 200 withdata.errorpresent anddata.tools = []. Only protocol, authentication, and internal errors use the standard error envelope. - The response uses sparse fields: on success
erroris omitted rather than sent asnull, andtargetis omitted when the locator could not be uniquely resolved.toolsis always present.
Authorizations
App key issued from the Flashduty console under Account → APP Keys. Required on every public API call. Keep it secret — it grants the same access as the owning account.
Body
Target identifier (host name, MySQL address, …). Max 256 bytes; no whitespace, control characters, or |.
Optional consistency check. Must equal the authenticated account when supplied.
Optional target kind. When omitted, webapi infers it from current target routing. If the call returns ambiguous_target_kind, retry with a value from target_kinds.
Response
Success
Success response envelope. On every 2xx response, request_id identifies the call (also mirrored in the Flashcat-Request-Id header) and data holds the endpoint-specific payload. Failure responses use a different shape — see ErrorResponse.