Skip to content

entherium_list_defects

Status: GA Access: token required API contract: 0.3.0 · capability 2026-09-03.1 View as Markdown Open in Claude Open in ChatGPT

READ the defect board (defects + incidents), newest first. Call this BEFORE filing a defect, to check it is not already reported. Filter by status (“open” | “closed”) and/or severity. Returns {“count”: N, “defects”: [{defect_id, title, status, severity, component, spec_ref, reporter, last_seen}]}. Needs the manage_task capability. (A per-defect change log does not exist yet — only tasks carry one.)

Access: read-only — safe to call repeatedly, changes nothing

Available at: /mcp/, /mcp/readonly/

Hints declared to MCP clients (ToolAnnotations)

HintValue
readOnlyHinttrue
destructiveHintfalse
idempotentHinttrue
openWorldHintfalse
NameTypeRequiredDescription
statusstring | nullnoopen or closed; omit for both
severitystring | nullnosev1 … sev4
limitintegernoMaximum number of defects to return

Send inside an initialized MCP session (see Connecting). Every parameter is shown with a typed placeholder; drop the optional ones you do not need — but for defect/task tools the QA fields are what keeps a report out of quarantine.

{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "entherium_list_defects",
"arguments": {
"status": "<status>",
"severity": "<severity>",
"limit": 1
}
}
}
FieldTypeDescription
countinteger (optional)Number of rows returned
defectsarray of object (optional)Defects and incidents, newest first
defects[].defect_idintegerTicket id on the board
defects[].titlestring
defects[].statusstringTicket status
defects[].severitystring | nullSeverity (sev1 … sev4), if set
defects[].componentstring | nullComponent the defect is filed against
defects[].spec_refstring | nullFeature id (opaque SPEC-NNN), if any
defects[].reporterstring | nullReporter identity as recorded
defects[].last_seenstring | nullISO-8601 time the defect was last observed
errorstring (optional)Present only when the board could not be read
SymptomCauseAction
401Token missing/expiredTokens are issued by the platform owner via POST /api/v1/auth/agent-token (superuser-only) — ask for a re-issue. ⚠️ A new token replaces your grant set
403 / capability errorYour token lacks the capability or the contract grantCheck my_capabilities first; ask the owner for the grant