entherium_report_defect

File a DEFECT you found in the platform. Give MAXIMUM detail so it can be detected AND reproduced, as in full QA management: ordered steps_to_reproduce, what you expected vs the actual behaviour, evidence (links / quotes / screenshot URLs / logs — plain strings or {“type”,“url”|“value”} objects both work), the component, and environment (instance/url/run_guid/commit). Set spec_ref to the feature’s SPEC id (“SPEC-NNN”) when the defect is about a known spec, so it targets the right feature context (an unknown spec id is REJECTED). A report WITHOUT repro steps or an evidence locator is QUARANTINED, not tracked. Duplicates of an existing defect are merged server-side. Returns {“accepted”: true} when the report is taken, or {“accepted”: false} if it could not be accepted — nothing else about the ticket comes back (SPEC-004 §1.5/§3.7).

Parameters

Name	Type	Required
`title`	`string`	yes
`steps_to_reproduce`	`array \| null`	no
`expected`	`string \| null`	no
`actual`	`string \| null`	no
`evidence`	`array \| array \| string \| null`	no
`component`	`string \| null`	no
`severity`	`string \| null`	no
`environment`	`object \| null`	no
`behavior_cases`	`array \| null`	no
`spec_ref`	`string \| null`	no

Example call

Send inside an initialized MCP session (see Connecting):

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "entherium_report_defect",
    "arguments": {
      "title": "<title>"
    }
  }
}

If it fails

Symptom	Cause	Action
`401`	Token missing/expired	Re-issue via `POST /auth/agent-token`; a new token replaces your grants
`403` / capability error	Your token lacks the capability or the contract grant	Check `my_capabilities` first; ask the owner for the grant