Skip to main content
GET
List tools needing attention
The reference panel describes the current v3 operation. The notes below describe its v2 compatibility API. Follow the v3 request schema for current calls: v3 can move identifiers from the body or query into the URL. Keep the v2 method, path, and payload together when using the compatibility API.

v2 compatibility notes

GET /api/v2/tools/listNeedingAttention?limit= lists the tools that need attention, as the tool catalog’s attention banner does. Like the Console, it checks tools of any status.

Authority

You need tools:read at the platform scope. An unavailable store is a 500. A repeated or out-of-range parameter is 400 bad_request.

What it returns

Each row is a toolId and its reasons: invalid_schema when its input schema is not valid JSON Schema, disabled when it is disabled. limit is 1-50 (default 10). meta.partial is true when the catalog held more tools than were read.

Authorizations

Authorization
string
header
required

An External App: the JWT it obtains from POST /oauth/token with OAuth2 client_credentials. Pass as Authorization: Bearer <jwt>. An app's static companion key also authenticates as the app, but is deprecated and is not protected by Idempotency-Key.

Query Parameters

limit
integer
default:10

Items per page, 1 to 50 (default 10); a larger value is a 400 too_big. A page may hold fewer items than limit while meta.hasMore is true; continue with meta.nextCursor.

Required range: 1 <= x <= 50
cursor
string

The previous page's meta.nextCursor; any other value is 400.

Minimum string length: 1

Response

List tools needing attention

data
object[]
required
meta
object
required

A list page's continuation. While hasMore is true, nextCursor is a string: pass it as cursor for the next page. hasMore: false ends the list; with truncated: true, more exist past what this list reads, and no cursor reaches them.